4 ms·
The problem is that their marketing and docs make it sounds like it is the solution for everything. Legacy Cassandra workload? Use CosmosDB Graph Database? Us
by outside1234 8y ago
The 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]