Comments on: More on Twitter, Rails, and Scaling http://shebanator.com/2007/04/19/more-on-twitter-rails-and-scaling/ Thoughts on Dynamic Languages, Web Apps, and more Wed, 04 Nov 2009 18:42:52 +0000 hourly 1 http://wordpress.com/ By: Studiowhiz.com » Blog Archive » Do you always need a database? http://shebanator.com/2007/04/19/more-on-twitter-rails-and-scaling/comment-page-1/#comment-245 Fri, 20 Apr 2007 17:45:21 +0000 http://shebanation.wordpress.com/2007/04/19/more-on-twitter-rails-and-scaling/#comment-245 [...] saw an interesting update on the Twitter story. One of the best parts though was the link they provided to this [...]

]]> By: Peter Bell http://shebanator.com/2007/04/19/more-on-twitter-rails-and-scaling/comment-page-1/#comment-244 Fri, 20 Apr 2007 03:01:04 +0000 http://shebanation.wordpress.com/2007/04/19/more-on-twitter-rails-and-scaling/#comment-244 Thanks for the mention :->

Just in case the conversation *does* take a downturn again, I’m not saying Rails or Ruby can’t scale. Only questioning the choice of a language and framework designed to speed development at the cost of performance for an application where performance rather than speed of development is probably the main driver!

Personally I’d prototype Twitter in *insert-cool-dynamic-language-here* and then if performance was an issue, once the interfaces were pretty well locked I’d get a second team to re-code the app using a more performance oriented stack.

I develop a lot using ColdFusion which blends the benefits of dynamic typing with enough OO support, a great set of tag libs and a built in templating language for both templating views and code gen (which is what I’m usually doing).

I wouldn’t hesitate to prototype in CF and then have a team port some or all of an app to a different language if performance was way more important than how quickly I could add new features.

]]>