3 ms·
CosmosDB does have problems but the comments here seem to mostly be about not understanding the data model. It's a JSON-based document-store that distributes da
by manigandham 8y ago
CosmosDB does have problems but the comments here seem to mostly be about not understanding the data model. It's a JSON-based document-store that distributes data across partitions.
It offers several interfaces (set at the database level) but that doesn't mean all the functionality is supported. It works well with MongoDB, Cassandra, and Table storage but you won't get relational SQL joins or fast graph search queries in Gremlin.
I agree that marketing and documentation is poor which leads to these misunderstandings. Multi-model is never perfect and people forget that emulation has a cost in performance, price and functionality.
- outside1234 8y agoThe problem is that their marketing and docs make it sounds like it is the solution for everything. Legacy Cassandra workload? Use CosmosDB Graph Database? Use CosmosDB Legacy MongoDB database? Use CosmosDB SQL Server database? Use CosmosDB When the only really valid use case is: Document Database? Use CosmosDB
- manigandham 8y agoYes, I said exactly that. Multi-model is a hard problem and only really works with similar data models. It's also confusing since people conflate SQL and relational semantics when it's really just a query language. It does work well enough if you have an OLTP document use-case like MongoDB, Cassandra, and JSON/SQL.
- dagss 8y agoDisagree about "conflate". SQL is very geared towards relational semantics. They may be independent in theory (a stretch), but any non-trivial SQL query (say a medium sized one with 50 lines abd 10 tables) is meaningless without a relational DB underneath. What Cosmos calls "SQL" is not SQL at all, it lacks almost everything, it just borrows a few keywords. If you cant even do inner joins and left joins and so on between different tables, it is NOT anything close to SQL. Joins is sort of the point of SQL.
- deleted 8y ago[deleted]