On 26/10/2010 11:27, Shane Hathaway wrote:
> On 10/26/2010 04:04 AM, Anton Stonor wrote:
>> In order to scale an application using RelStorage I was thinking about
>> seperating reads and writes accross databases. Writes would go to a
>> Mysql master and the app would read from one or more Mysql slaves.
>
> If you mean that you intend to set up some clients to write to a master
> database, while other clients only read from asynchronous replicas, then
> yes, you'll be in good shape. You should be able to get amazing
> scalability that way.
Wouldn't this require zero replication lag?
Even if the read replicas had only a second or two delay (or spike
delays caused by large writes?), would there not potentially be quite
serious problems?
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
