为什么 Cosmos DB 多个写入区域不能保证区域中断期间的写入可用性？
Cosmos DB 文档 (https://learn.microsoft.com/en-us/azure/cosmos-db/high-availability#what-to-expect-during-a-cosmos-db-region-outage）说“鉴于内部 Azure Cosmos DB 架构，使用多个写入区域并不能保证区域中断期间的写入可用性。在区域中断期间实现高可用性的最佳配置是具有服务管理故障转移的单个写入区域。”
这是否意味着多区域写入仅用于分配可用性有限的工作负载？ Azure Cosmos DB 的内部架构是什么？在哪里可以获取它？
根据我的理解，如果一个区域发生中断，则该区域的所有写入都应重定向到其他区域写入并无缝更新数据库。正确吗？
Cosmos DB documentation (https://learn.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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论