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.
That is what I want. Sounds great.
My assumption was that if a client was reading from a relica before fresh
data was replicated I would get old data. That was why I was talking about
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org