title: database replication lag (latency) with master-write and slave-reads
body: <p>We have a read-write master and replicated slave-read servers. In certain web use cases the data is posted and immediately read to be sent back to the server. The immediate read is done on the read-slaves and due to latency the data is not yet updated there. </p>
  
  <p>I understand this could be a common issue with a replication setup, we are new to this, would really appreciate any inputs on the options we have to overcome the situation.</p>
  
  <p>I can think of a few options right now:</p>
  
  <ul>
  <li>Always do immediate reads from the master.</li>
  <li>Decrease Latency by using powerful servers.</li>
  <li>Do away with replication and shard the DB.</li>
  </ul>
  
  <p>Thanks,
  Chris.</p>