Re:Twittering About Architecture
by gruseom on Thursday May 22, 2008 @04:37PM
(#197538)
The post says little that's specific. What it does say - our problem is different, it's hard, we're making progress - might all be true, but these are also the kinds of things people say when a software project is in trouble. It's hard to tell anything at all from reading the post.
[ Parent
| on HN ]
Well, what it lacks in specificity it makes up for by way of the lack of finger-pointing that we'd seen in the past from the Twitter team.
They did call out one of the many "why is it so hard to scale twitter" posts as being "one of their favorites":
http://www.hueniverse.com/hueniverse/2008/03/on-scaling-a-mi...
Everyone should read this blog post and the 2 followups. It brings a lot of insight into the parts of Twitter that bring it down and it has nothing to do with the message pushing part of Twitter.
I have a Jabber bot running that is hooked into the entire public timeline and it continues to run even when the main website has gone down. I don't think you can directly compare Twitter's issues with issues of Meebo, AIM, GTalk, etc.