title: When writing to azure table storage we sometimes see behavior
body: <p>When writing to azure table storage we sometimes see behavior that looks like the following situation:</p>
  
  <ol>
  <li><p>We send an update request “The update is received and queued for actual processing in azure“</p></li>
  <li><p>We receive an 200 OK result on the update request</p></li>
  <li><p>We send a request for data</p></li>
  <li><p>We get data from before the update (undesirable situation)</p></li>
  <li><p>We “wait a bit”</p></li>
  <li><p>We send another request for data</p></li>
  <li><p>We get data from after the update</p></li>
  </ol>
  
  <p>When azure is busy, the update seems to take a while, which becomes a problem if we query the updated data immediately (eventual consistency).
  Are the above assumed inner workings of azure correct?</p>
  
  <p>If so, what are best practices for getting up to date data directly after an update?</p>