Amid all the downtime, quite a few fans and haters of the micro messaging service Twitter have taken the opportunity to wax poetic about what Twitter should be doing to solve its issues. Now Twitter developer Alex Payne has responded on the Twitter Developer Blog.
The basic gist: Twitter was built the wrong way, now we must re-build it one piece at a time. This will take awhile. Come work for us!
According to Payne, Twitter was originally architected not as a messaging service, but rather as a kind of content management system (CMS). Because of this, Twitter has had major scaling issues over the past year and change — issues we’ve all experienced in both the system being down and general slowness.
While Payne states that the system as it exists today is much better than it was a year ago, there is still much work to be done. He hopes that one day the idea of simply “throwing more machines at it” will work (more or less) for scaling. Yet he warns, Twitter is not at that point yet and it will be slow-going to get there as Twitter is not about to shut the entire service down for a re-build from scratch.
Says Payne:
Our direction going forward is to replace our existing system, component-by-component, with parts that are designed from the ground up to meet the requirements that have emerged as Twitter has grown. First and foremost amongst those requirements is stability. We’re planning for a gradual transition; our existing system will be maintained while new parts are built, and old parts swapped out for new as they’re completed. The alternative - scrapping everything for “the big rewrite” - is untenable, particularly given our small (but growing!) engineering and operations team.
Interestingly enough, Payne doesn’t once mention Ruby on Rails, the framework on which Twitter is built that a lot of people (commenters on this blog and others at least) seem to have a major problem with. There were even rumors that Twitter was going to abandon Ruby on Rails. The service denied those rumors.
Payne also takes the time to mention that Twitter is hiring — no doubt thanks in part to that new round of funding that is rumored to have closed.
If you want to make Twitter better, there’s no more direct way than getting involved in our engineering efforts. We love kicking around ideas, but code speaks louder than words.
Indeed.
3:58 pm
WinExtra » The Twitter Obligation said:
[...] Internet time is a purely subjective measurement. So following a couple of excellent posts by MG Siegler at VentureBeat and Nik Cubrilovic at TechCrunch where they both talked about Twitter coming clean for a change [...]
11:20 pm
The only thing Twitter has to fear, is Twitter itself » VentureBeat said:
[...] culminating in an admission that it isn’t sure what is wrong and that it will basically need to be re-built. As anyone who has read any of my dozen or so posts about Twitter over the past couple weeks will [...]
9:52 pm
Twitter: Still not working, but explaining why on Twitter Status blog » VentureBeat said:
[...] company to provide quick updates when something breaks — or as the case may be, something is fixed. That was in fact the case tonight as Twitter announced that the pagination feature of the site had [...]
11:23 pm
Twitter: Don’t blame Ruby, blame Scoble » VentureBeat said:
[...] One thing is for certain with all of Twitter’s recent issues. A lot of start-ups in the future are going to learn from mistakes made. Today’s post follows Payne’s post last week stating that Twitter wasn’t built to handle its current usage. [...]
12:37 am
scot hacker’s foobar blog » Notes on Twitter said:
[...] better. There are rumors that the rebuilt components are all written in PHP, though the company denies the rumors. Music: Minutemen :: No Parade Filed under: Blogging, Microblogging, Twitter @ 12:36 [...]
12:52 am
FriendFeed takes noisy tracks and makes a best-of collection » VentureBeat said:
[...] and more popular because more and more people are using it. However, because of this popularity, fundamental flaws in its architecture have been exposed and the service is constantly [...]
6:34 pm
Can Twitter survive the WWDC Stevenote? » VentureBeat said:
[...] of you may recognize that Twitter’s recent downtime issues are a result of its architectural problems exposed by its rapid growth. However, back in the day (that is, January and the preceding months), [...]
12:28 pm
Pivotal Labs to help rebuild Twitter following persistent downtime issues » VentureBeat said:
[...] as it has continued to grow (not unlike ourselves, as our readers may have noticed earlier today). Twitter has recently improved, managing to mostly stay up during large events like Apple’s Worldide Developer Conference [...]
12:00 pm
No, you’re not driving away your Twitter friends, Twitter may be just cleaning house — or losing data » VentureBeat said:
[...] if Twitter was deleting spam accounts, but the company did just hire Pivotal Labs to help solve its woes. Those guys weren’t supposed to start until Monday, but perhaps they’re diving right in [...]
4:32 pm
A Payne in the Twitter Fail Whale’s side » VentureBeat said:
[...] has done a good job answering questions about Twitter’s issues on the site’s blogs and apparently is pretty good as his actual job as [...]