You'll probably want to look at replication [1] and/or sharding. There are several gems out there that will help you do one, the other, or both within Rails. I haven't used any of them, but some quick googling seem to indicate that data_fabric [2] or masochism [3] might be good places to start.
While googling I also ran across MySQL's HA/Scalability Guide which looks useful if this is something new to you. dwh [1] http://dev.mysql.com/doc/refman/5.1/en/replication-solutions.html [2] http://blog.fiveruns.com/2008/7/9/introducing-data_fabric [3] http://github.com/technoweenie/masochism/tree/master [technoweenie always chooses the best project names...] [4] http://dev.mysql.com/doc/mysql-ha-scalability/en/index.html internetchris wrote: > Hey Everyone, > > I'm looking for some advice. I am developing an application that will > have several million transaction records. I've heard of people scaling > Rails to connect to multiple databases. I have never done this, and > I'm wondering if rails can look at multiple databases and treat them > as one, or if I design some sort of overload feature that makes it > trickle from one database to the next. In essence I don't want my > rails application to be limited by database capability or size. As I > said before I have never designed an app like this, and I want to get > it right before I get too far into the application. I have just > started the coding, and would like to be proactive on making the right > decision. > > Thanks! > > Chris > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
