title: Are Message Queues the right tool for geographically distributed deployments?
body: <p>Our scenario is as follows (which I guess is not unique): we have our database backed web apps in two different colocation facilities. One facility has the master database, the other one has the slave. </p>
  
  <p>We want the slave facility to keep working (in limited mode if necessary) even if the master database is offline. When the master database comes backup, the data should get synchronized.</p>
  
  <p>I was thinking that I can use messages queues to send the data update instructions. The message queue in the slave server will hold its messages if there is a disconnect between the slave and master servers. When the connection comes back up the messages will flow and the master server will update the database.</p>
  
  <p>Am I missing something? Is this not a good use for message queues?</p>