Re:Azure Cosmos DB, a globally distributed database
by strmpnk on Wednesday May 10, 2017 @02:02PM
(#14310214)
Having evaluated both, I'd say Cloud Spanner is quite a bit behind in some regards. It's not that Spanner itself can't do something but that Cloud Spanner hasn't productized some important features like multi-datacenter failovers. It's certainly coming but CosmosDB (aka. DocumentDB) does a lot of this today (and has been for awhile as this is not entirely new).
[ Parent
| on HN ]
Re:Azure Cosmos DB, a globally distributed database
by azurezyq on Wednesday May 10, 2017 @02:25PM
(#14310398)
But from Cosmos DB's doc, cross-dc strong consistency seems not even supported.
https://docs.microsoft.com/en-us/azure/documentdb/documentdb...
"Azure Cosmos DB accounts that are configured to use strong consistency cannot associate more than one Azure region with their Azure Cosmos DB account."
Re:Azure Cosmos DB, a globally distributed database
by strmpnk on Wednesday May 10, 2017 @02:45PM
(#14310563)
I didn't claim cross-dc consistency. I said failover, which is shockingly hard to make many competitors do. The key here is that only one DC can take writes but the failover works transparently with your client (also with clear SLAs).
Re:Azure Cosmos DB, a globally distributed database
by lern_too_spel on Wednesday May 10, 2017 @11:09PM
(#14313591)
Why do you need failover if you have global multimaster like Spanner?
Re:Azure Cosmos DB, a globally distributed database
by aliuy on Wednesday May 10, 2017 @11:16PM
(#14313616)
An interesting thing to point out is the current beta for Cloud Spanner does not have multi-region deployments... and instead, allows you to do single-region deployment in your choice of 3 (not >30) regions:
https://cloud.google.com/spanner/docs/instance-configuration