'Why doesn't Cosmos DB multiple write regions guarantee write availability during a region outage?
Cosmos DB documentation (https://docs.microsoft.com/en-us/azure/cosmos-db/high-availability#what-to-expect-during-a-cosmos-db-region-outage) says that "Given the internal Azure Cosmos DB architecture, using multiple write regions doesn't guarantee write availability during a region outage. The best configuration to achieve high availability during a region outage is single write region with service-managed failover."
Does that mean multi-region writes is just for distributing workloads with limited availability? What is the internal Azure Cosmos DB architecture and where can I get it?
In my understanding, if there is an outage in one region, all writes from that region should be re-directed to other region writes and seamlessly update the database. Is it correct?
Solution 1:[1]
During the outage, ensure that there are enough provisioned RUs in the remaining regions to support additional traffic. When the outage is over, you may re-adjust provisioned RUs as appropriate.
The internal Azure Cosmos DB architecture is basically document of azure cosmos db in this document they gave all information regarding cosmos db its architecture, design, availability, latency, consistency model, etc.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | PratikLad-MT |