On Apr 25, 12:25 pm, jcBAM <[email protected]> wrote: > I was told Ruby on Rails has limitation in scalability...
As does everything else, I would say. A reasonable practice is to build you app, then profile it when it becomes slow. See where the speedups are: maybe it's MySQL settings, more RAM on the servers, more hardware/instances, tighter Ruby. If, in your profiling, you identify a routine - or subsystem that you really can't get speed out of, figure out how to write it in something else. Maybe you - as Twitter has - spin off to another language for parts of your app. Maybe you write a gem in C to get that speed boost. Maybe node.js, for high concurrent connections in a special case. There's also knowing what Rails is good at, and what it's not. For example, this weekend a client and I were talking about how to implement a live widget (ala Facebook's news feed). We talked for a little bit about how Rails doesn't make that kind of thing easy, and ended up looking at http://www.pusher.com to provide that functionality in the app. However, I believe that knowledge comes from knowledge/experience of how the web works, known-how on the Rails side, plus knowledge of your own application and goals. In short: premature optimization is the route of all evil (except when it's not) :) Hope this helps, _Ryan Wilcox -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
