Comments on: How to Make Twitter Scalable http://www.appistry.com/blog/2008/04/how-make-twitter-scalable/ News and Ideas from Appistry on Appistry, Cloud Computing, Private Clouds and More Wed, 13 Jan 2010 07:37:17 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: McWong http://www.appistry.com/blog/2008/04/how-make-twitter-scalable/comment-page-1/#comment-51 McWong Tue, 30 Nov 1999 00:00:00 +0000 #comment-51 I put up a similar post a few days ago... http://www.themcwongs.com/mcblog/2008/04/twitter-jabber-stability-shoul.html. Twitter is a message router, not an MVC app. The focus recently is "oh, they use rails, that's why they don't scale..." but as Twitter founder ev points out (http://twitter.com/ev) there is a lot of code there that isn't rails. Striking the appropriate balance is what's key, and shifting more to the approach outlined here is very reasonable. I put up a similar post a few days ago… http://www.themcwongs.com/mcblog/2008/04/twitter-jabber-stability-shoul.html. Twitter is a message router, not an MVC app. The focus recently is “oh, they use rails, that’s why they don’t scale…” but as Twitter founder ev points out (http://twitter.com/ev) there is a lot of code there that isn’t rails. Striking the appropriate balance is what’s key, and shifting more to the approach outlined here is very reasonable.

]]> By: AkitaOnRails http://www.appistry.com/blog/2008/04/how-make-twitter-scalable/comment-page-1/#comment-53 AkitaOnRails Tue, 30 Nov 1999 00:00:00 +0000 #comment-53 Another FUD article from someone who obviously knows nothing about Rails. Another FUD article from someone who obviously knows nothing about Rails.

]]> By: Luigi Montanez http://www.appistry.com/blog/2008/04/how-make-twitter-scalable/comment-page-1/#comment-54 Luigi Montanez Tue, 30 Nov 1999 00:00:00 +0000 #comment-54 As a developer, I would never, in a million years, write a blog post supposing that I know how to build an application better rather than the actual developers who have worked on it for the past two years. What if I told you how to do your job? What if I went into that post about your Drupal commenting being buggy and told you, "Yeah, it's really not that hard to get Drupal commenting to work. Just follow these three one-sentence steps and it'll work right quick." You never know what goes into any project or application unless you actually work on it. Or, at the very least, do at least some research about it. If you did, you would have found out that Twitter's core does in fact run on a message queue system that's not Rails at all, but pure Ruby: http://dev.twitter.com/2008/01/announcing-starling.html Daemons, asynchronous messaging, memcached. Sounds like your first three bullet points right there. Pardon them if they don't follow your fourth. As a developer, I would never, in a million years, write a blog post supposing that I know how to build an application better rather than the actual developers who have worked on it for the past two years.

What if I told you how to do your job? What if I went into that post about your Drupal commenting being buggy and told you, “Yeah, it’s really not that hard to get Drupal commenting to work. Just follow these three one-sentence steps and it’ll work right quick.”

You never know what goes into any project or application unless you actually work on it. Or, at the very least, do at least some research about it. If you did, you would have found out that Twitter’s core does in fact run on a message queue system that’s not Rails at all, but pure Ruby:

http://dev.twitter.com/2008/01/announcing-starling.html

Daemons, asynchronous messaging, memcached. Sounds like your first three bullet points right there. Pardon them if they don’t follow your fourth.

]]>