Welcome to Stratos!
By various metrics Twitter is the biggest Rails site on the net rightnow. Running on Rails has forced us to deal with scaling issues
At this point in time there’s no facility in Rails to talk to more than one database at a time. The solutions to this are caching the hell out of everything and setting up multiple read-only slave databases, neither of which are quick fixes to implement. So it’s not just cost, it’s time, and time is that much more precious when people can[’t] reach your site.None of these scaling approaches are as fun and easy as developing for Rails
All the convenience methods and syntactical sugar that makes Rails such a pleasure for coders ends up being absolutely punishing, performance-wise. Once you hit a certain threshold of traffic, either you need to strip out all the costly neat stuff that Rails does for you (RJS, ActiveRecord, ActiveSupport, etc.) or move the slow parts of your application out of Rails, or both.
All of us working on Twitter are big Ruby fans, but I think it’s worth being frank that this isn’t one of those relativistic language issues. Ruby is slow.
Pues igual tengo que plantearme el usar o no un framework... porque la web tendra muchos muchos muchos usuarios simultaneos pidiendo y enviando info al server , muchas sesiones simultaneas , etc.... a ver si la almohada me ayuda a pensar mejor ( y mañana leo lo que me digais tb )