Twitter suffering from Ruby on Rails Performance
This is a nice interview with one of the developers of Twitter, talking about the issues they face with Ruby on Rails when it reaches peak usage. Apparently the site is getting around 11,000 hits a second on peak times, and since Rails cannot talk to more than one database at a time, this is causing big time delay for end user. This does not mean we should all keep away from Ruby on Rails, as it a great potential in cutting down development cycles, and enforcing the MVC. Unless you are planning of building a site that will receive this massive hit, I guess RoR would do just fine.
Popularity: 12% [?]
Most Popular Posts:
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
Comments
Well, to be honest I never used Twitter. I was shocked by the posted traffic amount. Note about not updating your account in 24 hours! That’s a lot to ask from users on the long run.
Perhaps they only do it for short period as notice, if you don’t update they assume you don’t want those notes anymore.
Twitter automatically sent me a msg saying that I have not updated my status in 24 hours! It was pretty sweet! I really liked the concept when I saw my friend using it and so I signed up but for some reason it works perfectly for him but not for me!
I kinda use Twitter! I signed up for it and it worked fine for a few days! I used to get my friend’s Twitter notes and I got the Twitter note about not updating my account in 24 hours! After those few days, I don’t know what happened but I do not get any Twitter msgs not even from Twitter itself!