Re:Azure Cosmos DB, a globally distributed database
by aravindkr1 on Wednesday May 10, 2017 @04:23PM
(#14311311)
The latency SLAs are within the same Azure region. You can distribute your data across any of the 30+ regions that Azure is available in. Your apps always read from the local/closest region with the homing APIs.
[ Parent
| on HN ]
Re:Azure Cosmos DB, a globally distributed database
by xapata on Thursday May 11, 2017 @09:59AM
(#14316023)
That didn't answer the question: will all regions be always consistent?
Re:Azure Cosmos DB, a globally distributed database
by GovindMS on Thursday May 11, 2017 @10:44AM
(#14316368)
We would invite you to explore the consistency levels available in Cosmos DB. As a developer you can choose what makes most sense in distributed scenario. https://docs.microsoft.com/en-us/azure/documentdb/documentdb...
Eventual is one end of the consistency. But then consistent prefix, session (if you can control) and bounded staleness all can play a role.