Setting the appropriate consistency level for operations
When you use distributed databases that rely on high availability and low latency, you can choose between two different extreme consistency models: strong consistency and eventual consistency. The former is the standard for data programmability, but this will result in reduced availability during failures and higher latency. The latter offers higher availability and better performance, but makes it much harder to program applications.
Azure Cosmos DB offers more choices between the two extreme consistency models. Strong consistency and eventual consistency are at two different ends of the spectrum. This can help developers make a more precise choice with respect to high availability and performance. Azure Cosmos DB offers five consistency models, known as strong, bounded staleness, session, consistent prefix, and eventual consistency:
- Strong: Strong consistency is the easiest model to understand. The most recent committed...
