AJAX and master/slave architecture

Hi *,
I’m scaling a pretty huge application written in RoR.
I’ve decided to have n read-only slave databases, and a single master
for write operations.

The problem I’m facing is that when I write using Ajax calls the
master database doesn’t replicate the data on slaves fast enough, so
it doesn’t render the correct data (even worse - it memcaches the
wrong data …).

Someone has suggestions ? How are master/slave architectures normally
handled by huge players in the Rails community ? I’m thinking about
stuff like a timer to stop the read and give the master the time to
replicate, but it seems too ugly for working :stuck_out_tongue:

TIA,
ngw

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs