What's wrong with Twitter? CoolAcid knows.

if you are Twitter-savvy, then you know that one of the most popular topics when it comes to Twitter is its reliability. There are more jokes and comments about Twitter being down again then you can imagine; and I'm talking on Twitter itself! Anyhow, our resident Joomla! wizard, Jason Kendall (aka CoolAcid) has a theory about that, one that starts to make a lot of sense.

Ok - So I've noticed twitter was not on my IM anymore. I regularly post via my gmail account on my rim. I didn't think much of this. Marcel sent me an invite to plurk, and some posts on his lug-nuts list showed signs of twitter problems, so I decided to go over to the site to see what's what. Seems they've been having issues for a while - I started off my journey to a "we're down" page. But! The blog is up, so I mossy on over there to see what's what. I found this entry: It's Not Rocket Science, But It's Our Work - Here we have a link to the infamous status page. We also have some Q/A which yielded: Q: Is it true that you only have a single master MySQL server running replication to two slaves, and the architecture doesn’t auto-switch to a hot backup when the master goes down? A: We currently use one database for writes with multiple slaves for read queries. As many know, replication of MySQL is no easy task, so we've brought in MySQL experts to help us with that immediately. We've also ordered new machines and failover infrastructure to handle emergencies. Ok, Their having problems, according to the site. Maybe I can help them out, over to the jobs page and they're looking for a Systems Eng:

Check out his Blog here to read the rest and learn more. Thanks for the sleuthing, Jason.