I'd like to see an in-depth comparison with Google Cloud Spanner.
Exactly, although cloud is not my best suite, I am so exited. This is serious fight.
Azure Cosmos DB, a globally distributed database
31–40 of 120 posts
Re: Azure Cosmos DB, a globally distributed database
#32> Latency: 99.99% of Impressive SLA to guarantee, I'm curious if this will hold up in all random customer workloads that are coming, e.g. updating a lot of fields in a large document (or just a very large insert).
We just did a benchmarking for a PoC on DocumentDB side-by-side Cassandra. It does the job, I have not yet seen anything revolutionary. Cassandra benchmarks seemed better.
Re: Azure Cosmos DB, a globally distributed database
#33Earlier quoted context omitted.
It's called Azure SQL DB (unless you want Mysql, then you'd want IaaS SQL DB)
With the exception that Azure SQL doesn't horizontally scale across regions/datacenters like Google Cloud SQL does.
I don't think Google Cloud SQL does either in a fully managed way. Spanner OTOH does that but it's NewSQL. Traditional sharding has been supported for a while: https://docs.microsoft.com/en-us/azure/sql-database/sql-data.... you can create databases where ever you want.
Re: Azure Cosmos DB, a globally distributed database
#34I'd like to see an in-depth comparison with Google Cloud Spanner.
Is there a real life case study of people/startup using Cloud Spanner? I am wondering what are the use cases of Spanner that cannot be fulfilled by other Google Cloud Platform products.
Re: Azure Cosmos DB, a globally distributed database
#35Is it open source? Why do I care? The same reason I don't use AWS or Google Cloud only datastores: I want to avoid vendor lockin.
Vendor lock in is a bad example, it's not like you're going to move your infrastructure from AWS to Google every 6months. And if you do you will have many more complicated problems than vendor lock in.
Re: Azure Cosmos DB, a globally distributed database
#36I'd like to see an in-depth comparison with Google Cloud Spanner.
Is there a real life case study of people/startup using Cloud Spanner? I am wondering what are the use cases of Spanner that cannot be fulfilled by other Google Cloud Platform products.
relational model
globally distributed ACID transactions
99.999 availability
to name a few
Re: Azure Cosmos DB, a globally distributed database
#37Hi, This is Dharma from Azure Cosmos DB team. We are super excited to make the service available today.We published the first of the series of technical blog posts here -> https://azure.microsoft.com/en-us/blog/a-technical-overview-.... Would love to answer any Cosmos DB questions.
Re: Azure Cosmos DB, a globally distributed database
#38Re: Azure Cosmos DB, a globally distributed database
#39Very interesting DB service. If I'm reading the docs right it sounds like you can't do JOINs across documents?
https://docs.microsoft.com/en-us/azure/documentdb/documentdb...
Re: Azure Cosmos DB, a globally distributed database
#40This isn't a new database. This is a rebranding of the generically-named Azure DocumentDB, plus some new features.
Not really. It's a new database and is a superset of DocumentDB.
Azure Cosmos DB has been many years in the making. Azure Cosmos DB started as “Project Florence” in late 2010 to address developer the pain-points faced by large scale applications inside Microsoft. Observing that the challenges of building globally distributed apps are not a problem unique to Microsoft, in 2015 we made the first generation of this technology available to Azure developers in the form of DocumentDB. Since that time, we’ve been steadily adding new capabilities both in the database engine as well as, larger distributed system components. Azure Cosmos DB is the result. It is the next big leap in globally distributed, at scale, cloud databases. As a part of this release of Azure Cosmos DB, DocumentDB customers, with their data, are automatically Azure Cosmos DB customers. They now have access to the new system and capabilities offered by Azure Cosmos DB today as well as, as we keep evolving the service.