I just thought it would be great if Rails supported multiple read databases and only one database for inserts/updates. Suppose we have an extremely popular site and we cannot turn on caching but we have money to buy a farm of 20 computers to manage the load. Sine 90 % of all queries (on average) are selects it would be sensible to set up 1 server as a main insert/update database master server and the rest of them as slaves used only for selects. It would be great if such a feature was added to Rails (specifying insert/update database as well as selects database if needed). Each Rails proccess would have to keep 2 connections open: 1 to the master and 1 to some slave server. FastCGI +Ruby + Rails scales well. What about scaling databases ? What''s your opinion ? -- Best Karol Hosiawa hosiawak-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
* Karol Hosiawa [2005-04-21 14:45]:> Sine 90 % of all queries (on average) are selects it would be sensible to > set up 1 server as a main insert/update database master serverI don''t know if there''s any support existing or planned in Rails, but memcached is probably a better path to pursue for this type of situation(?) It was written for just this purpose: Main site http://www.danga.com/memcached/ Ruby libs http://www.deveiate.org/code/Ruby-MemCache.html -- ______________________________ toddgrimason*todd-AT-slack.net