Designed with TLA+! :D Small interview with Leslie Lamport:<p><a href="https://techcrunch.com/2017/05/10/with-cosmos-db-microsoft-wants-to-build-one-database-to-rule-them-all/" rel="nofollow">https://techcrunch.com/2017/05/10/with-cosmos-db-microsoft-w...</a><p>Hope Cosmos team releases a whitepaper on their experiences with the language. I'd heard snatches of gossip here and there that TLA+ was used inside Cosmos, but no concrete details.<p>edit: apparently there's also a video of Lamport talking about this <a href="https://www.youtube.com/watch?v=L_PPKyAsR3w" rel="nofollow">https://www.youtube.com/watch?v=L_PPKyAsR3w</a>
Hi, 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 -> <a href="https://azure.microsoft.com/en-us/blog/a-technical-overview-of-azure-cosmos-db/" rel="nofollow">https://azure.microsoft.com/en-us/blog/a-technical-overview-...</a>. Would love to answer any Cosmos DB questions.
> Latency: 99.99% of <10 ms latencies at the 99th percentile<p>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).
Talk about the foundations of Cosmos DB: <a href="https://www.youtube.com/watch?v=Yfmw7swCtZs" rel="nofollow">https://www.youtube.com/watch?v=Yfmw7swCtZs</a>
I find this product slightly befuddling.<p>It seems like a "just throw all your data in this" kind of database, probably intended for everything but core application relational data (so, good for analytics, messaging, etc).<p>It sounds like the atom-record-sequence model at the heart of it is pretty key, but there's not a lot in the article about what that is and how it works. Is this a well-understood data structure used elsewhere?<p>The project seems very ambitious, and I could see it being used pretty heavily at a lot of companies. Thoughts?
I can't seem to find the old DocumentDB prices any more, but it seems like it's a lot cheaper now? Also, is User-Defined Performance something new? since last time I looked into DocumentDB you had to pay the monthly RU fee per 10GB disk.<p>One more thing, as someone who went from DocumentDb to Azure Storage (Tables) back in April 2016 because of the higher price, slower queries, and scalability problems, is there anything that may make Cosmos DB a better option?
Is Cosmos related to the work on Corfu/CorfuDB [2] [1] in any way?<p>[1] <a href="https://www.microsoft.com/en-us/research/publication/corfu-a-shared-log-design-for-flash-clusters/" rel="nofollow">https://www.microsoft.com/en-us/research/publication/corfu-a...</a><p>[2] <a href="https://github.com/CorfuDB/CorfuDB" rel="nofollow">https://github.com/CorfuDB/CorfuDB</a>
Very interesting DB service. If I'm reading the docs right it sounds like you can't do JOINs across documents?<p><a href="https://docs.microsoft.com/en-us/azure/documentdb/documentdb-sql-query#a-idadvancedaadvanced-database-concepts-and-sql-queries" rel="nofollow">https://docs.microsoft.com/en-us/azure/documentdb/documentdb...</a>
I don't see CosmosDB on the HIPAA compliance list, anyone know if there are plans to add it? <a href="https://www.microsoft.com/en-us/trustcenter/compliance/hipaa" rel="nofollow">https://www.microsoft.com/en-us/trustcenter/compliance/hipaa</a>
From the intro page[1]... Many of the descriptions comparing to NoSQL are wrong. There are plenty of NoSQL options that have similar features, though it isn't universal, it can and often is there. Cassandra, for example, probably does just as well in multi-zone/dc concurrency. Consistency options are also similarly tunable. Cockroach 1.0 was announced earlier as well.<p>It's not that I don't appreciate the option. This seems far closer to what DocumentDB should have been earlier on. Though tbh, I think Storage Tables are already pretty useful.<p>[1] <a href="https://docs.microsoft.com/en-us/azure/cosmos-db/introduction" rel="nofollow">https://docs.microsoft.com/en-us/azure/cosmos-db/introductio...</a>
Does it provide search?<p>It's a strange thing, but almost all new database technologies seem to leave search as an afterthought for some later day instead of starting on day one with the assumption that "it's all about search".<p>A database system that doesn't support rich search capabilities is restricted to very limited types of applications.<p>Often search is left unimplemented for years, or perhaps never implemented.
Does CosmosDB have any relationship to Microsoft Cosmos (<a href="http://web.stanford.edu/class/ee380/Abstracts/111026a-Helland-COSMOS.pdf" rel="nofollow">http://web.stanford.edu/class/ee380/Abstracts/111026a-Hellan...</a>)? Or is this another case of Dynamo / DynamoDB?
See <a href="https://www.youtube.com/watch?v=Yfmw7swCtZs" rel="nofollow">https://www.youtube.com/watch?v=Yfmw7swCtZs</a> by Turing Award Winner, Dr. Leslie Lamport, as he talks about Azure Cosmos DB
If I understood it correctly, they mentioned they offer horizontal scalibility for their databases and I wonder how does it work for the graph data model