When writing to azure table storage we sometimes see behavior

user_11663777 0
Viewed 91

When writing to azure table storage we sometimes see behavior that looks like the following situation:

  1. We send an update request “The update is received and queued for actual processing in azure“

  2. We receive an 200 OK result on the update request

  3. We send a request for data

  4. We get data from before the update (undesirable situation)

  5. We “wait a bit”

  6. We send another request for data

  7. We get data from after the update

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?

If so, what are best practices for getting up to date data directly after an update?

azure-table-storage azure-storage
1 Answers

I'm afraid that the situation is kind of normal.As we know,CAP has influenced so many data systems.Please refer to this detailed document.

The situation you described shows that azure table storage uses high availability, which guarantees that the service could be accessed by users at all times. However, this has a slight impact on consistency, and the data accessed by users may not be up-to-date.

You could know about cosmos db table-api,it supports 5 consistency levels,from Strong to Eventually.

enter image description here

If you do concern the real-time data,you could set the level as Strong.

user_81989460
Related