Welcome to AppFail
You last visited: 2010-09-08
If you know of a site or app that has failed, tell us right away
via PBJ, via Twitter or via this contact form. If we use your submission we'll attribute and link back to you.
Keep your head above water by keeping on top of the latest failures. Follow us on Twitter or subscribe to our RSS feed
- appfail: RT @scaleengine: August Usage Statistics for ScaleEngine: Outgoing Bandwidth: 27.5TB, HTTP Requests Edge: 565M, CDN: 60M, Origin: 193M. ...
- appfail: It is @dhewlett birthday. Tweet #dGeek & #HappyBdayDavidHewlett to trend. #McKay 0wnz you and you know it.
- appfail: Password Security Misconceptions: http://bit.ly/cAk0F9
- appfail: The anatomy of a DoS attack http://bit.ly/bDLOYE
- appfail: @Miss604 The story about your website inspired me to write an article explaining the different types of DoS attack. http://appfail.com/178
Welcome to AppFail
Posted on 2009-06-24
Infrastructure is all the various bits that hold a website up, like the piers of a bridge, or the legs of a chair. For your average blog or forum the most common failure is overloading the database, which happens when unoptimized queries lock tables for too long, or when a single database just cannot handle the volume of queries that are coming in. This results in the dreaded 'Too many Database Connections' error that is all too common on wordpress blogs submitted to digg. This is not actually the fault of wordpress, but of the poor choice in hosting provider by the blogger. A small investment in infrastructure will pay off every time. Another common problem is simply overloading the http servers capacity for concurrent connections. A single server can only answer a limited number of requests at any one time, and exceeding this limit generally causes an HTTP 503 error, or a connection timeout. The problem stems from that fact that you cannot just keep throwing hardware at the problem, a bigger server is still going to hit its limit eventually, and adding a second server, while it sounds easy, is not. How do you synchronize content, comments, and sessions across multiple servers? Now, you need to consider more than one database server, but how do you integrate new records added to separate database servers? The questions don't have easy answers, and the number of gotchas is endless. This is why it pays to have someone who has experience building and managing that infrastructure for you.
One of my pet peeves is when a favourite web comic is down because the newest comic has been submitted to digg, and I end up hammering refresh at a 503 error, or loading the page without the CSS or the images (the entire purpose of my visit). I understand a web comic doesn't generate a lot of revenue to pay for expensive infrastructure, but surely a more modern version of apache, or better yet, a fast httpd like nginx could service that load without breaking the site, or they could use a cloud solution like Amazon's Cloud Front service.
By: Allan Jude
Cuiusvis hominis est errare; nullius nisi insipientis in errore perseverare - Any man can make a mistake; only a fool keeps making the same one.
Digg Proof Hosting
The key to surviving Digg and Slashdot is Infrastructure. You can't get it from a regular web host, it requires experience. The High Load Hosting Experts at ScaleEngine can make your site thrive, and avoid having your site featured on AppFail.
Cyber Security Alerts
- Mozilla Releases Firefox 3.6.9
- Apple Releases Safari 5.0.2 and 4.1.2
- Apple Releases iTunes 10
- Google Releases Chrome 6.0.472.53
- Insecure Loading of Dynamic Link Libraries in Windows Applications
- VMware Releases Updates for ESX Service Console Packages
- Cisco Releases Security Advisory for IOS XR Software Border Gateway Protocol
- RealNetworks Releases Update to Address Vulnerabilities in RealPlayer
Page Generated in 181ms