Question - How Should I Think About Consistency Levels In The Table Api?
Answer -
Azure Cosmos DB gives properly-reasoned alternate-offs between consistency, availability, and latency. Azure Cosmos DB gives 5 consistency stages to Table API developers, so you can select the proper consistency model at the desk stage and make person requests at the same time as querying the statistics. When a patron connects, it can specify a consistency degree. You can trade the extent thru the consistency Level argument of CreateCloudTableClient.
The Table API affords low-latency reads with "Read your own writes," with Bounded-staleness consistency because the default.
By default, Azure Table garage affords Strong consistency inside a vicinity and Eventual consistency in the secondary places.