Rails - Apr 2008 - 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 :p

TIA,
  ngw
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---