Twitter Should Move Away from Ruby

http://pragdave.blogs.pragprog.com/pragdave/2009/04/twitter-should-move-away-from-ruby.html

by nreece • 17 years ago

4 5 17 years ago

pragdave.blogs.pragprog.com

ianbishop• 17 years ago

I'm not much of a web programmer but what does a scalable, concurrent language with low memory overhead look like? Does it exist?

lacker• 17 years ago

In practice it looks like C++ with a lot of custom libraries.

dawie• 17 years ago

I would write some custom thread safe application server that's designed to scale.

grunties• 17 years ago

Dear rubists: The move to Scala is besides the point, the battle is long over. Ruby on Rails is not scalable. End of. The beacon of scalability you hold up for us to gaze at in awe, Twitter, fixed just about all of its scalability problems with SQL caching. That's SQL caching, also known as 'bypassing Rails'. If you can't reduce the known facts to this obvious conclusion, you have no business arguing about scalability.

ZeroGravitas• 17 years ago

I don't understand why "SQL caching" means bypassing Rails.

I mean if you do whole page caching then you bypass Rails, after the first call. But if you're only caching the SQL call then you still need something to format it into HTML, which I'm guessing in Twitter's case is Rails.

You're also conflating Ruby (the language) and Rails (the web framework).

Twitter Should Move Away from Ruby

Related Stories