Scaling read queries with mysql is drop dead simple. Just add replicas. But you only have one server to do inputs on.Real simple. But a Quad core machine with a little memory, 16 GB, you can serve hundred thousand people easily. We do hundreds of thousands of heavy queries every minute on one box. Just create indexes, 'explain' is your friend.
Trausti On Tue, Oct 6, 2009 at 10:44 PM, Diego Bernardes < [email protected]> wrote: > > Hi, > > I got a application actualy running on mysql, but, due a contract with a > client, the application can get some complex queries and lots of users > (like 10x more users). > > Its a academic application, and the company we are negociating have 7k+ > students. > > Im worry about the database, its better stick with de mysql? migrate to > postgresql? > > Which one can scale better with quality? > > Thanks! > -- > Posted via http://www.ruby-forum.com/. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
