I’ve been using Twitter for a long time now, and I can’t remember a period of downtime quite as bad as the current one. Features have been disabled, and there’s no ETA for when everything will be back to normal. Who knows, maybe it won’t ever be. Which got me wondering about why Twitter’s reliability is so terrible. Is it the nature of the application, or is it something to do with the people behind Twitter?
What if Twitter had been built by a different team, a team with a pretty good track record for high-availability services? What if Twitter had been built by the Web Services team at Amazon.com?
I think it’s safe to say that things would be quite different:
- Reliable, redundant infrastructure
Twitter would be run inside Amazon’s high-availability data centers. We would never know (or care) that Twitter’s main database was named db006, nor would we ever wonder whether it has a good backup. We’d just know that if it’s good enough for Amazon, it’s good enough for us. - No wondering, “is Twitter working?”
Instead of wondering if Twitter is working correctly or waiting for Twitter messages or blog posts that explain what the problem is, Twitter would be part of the AWS Service Health Dashboard. We’d be able to see, at a glance, how Twitter is working now, and how well it has worked for the last month. This is what transparency is all about. - Twitter wouldn’t be free, but we’d be cool with that
Twitter would have had a business model from day one, and we’d all be cheering about how affordable it is. A pay-as-you-go model like all the other web services from Amazon would work quite well for Twitter. You get what you pay for, right? - Premium Support and SLAs
Speaking of getting what you pay for, Amazon would likely have realized that there are lots of different types of users, and they’d react accordingly. We’d probably have Premium Support for Twitter, to service support requests more efficiently. We’d also have Service Level Agreements. - We wouldn’t call it Twitter…
Of course, the service wouldn’t be called Twitter. In keeping with Amazon’s other services it would probably have a name like “Amazon Simple Messaging Service”, or SMS for short. Though I suppose that acronym is already taken!
I am a huge Twitter fan, and I really do hope that Ev, Biz, Jack, and the rest of the team get things working and fixed. With every passing hour of downtime though, I lose a little bit of faith. I wonder if Twitter would be better off in someone else’s hands.
Of course, if Twitter really had been built by AWS, there would be far more differences than just the items in my list above. The service may not be recognizable as Twitter!
That doesn’t mean that they couldn’t adopt some of these items as improvements, however. I’d love to see an official Twitter health dashboard, for instance. One can hope.
Even occasional
The latest shiny-new-toy that people seem to be playing with is
A month ago
As 

Are you a news junkie? Do you want to be the first to know about things? Look no further than