Need advice about which tool to choose?Ask the StackShare community!
Azure Cosmos DB vs Cassandra: What are the differences?
Developers describe Azure Cosmos DB as "A fully-managed, globally distributed NoSQL database service". Azure DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development. On the other hand, Cassandra is detailed as "A partitioned row store. Rows are organized into tables with a required primary key". Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.
Azure Cosmos DB can be classified as a tool in the "NoSQL Database as a Service" category, while Cassandra is grouped under "Databases".
"Best-of-breed NoSQL features" is the top reason why over 13 developers like Azure Cosmos DB, while over 96 developers mention "Distributed" as the leading cause for choosing Cassandra.
Cassandra is an open source tool with 5.23K GitHub stars and 2.33K GitHub forks. Here's a link to Cassandra's open source repository on GitHub.
According to the StackShare community, Cassandra has a broader approval, being mentioned in 337 company stacks & 230 developers stacks; compared to Azure Cosmos DB, which is listed in 24 company stacks and 23 developer stacks.
The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.
The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.
Cassandra is quite capable of the task, in a highly available way, given appropriate scaling of the system. Remember that updates are only inserts, and that efficient retrieval is only by key (which can be a complex key). Talking of keys, make sure that the keys are well distributed.
Scylla can handle 1M/s events with a simple data model quite easily. The api to query is CQL, we have REST api but that's for control/monitoring
i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra
By 55M do you mean 55 million entity changes per 2 minutes? It is relatively high, means almost 460k per second. If I had to choose between Scylla or Cassandra, I would opt for Scylla as it is promising better performance for simple operations. However, maybe it would be worth to consider yet another alternative technology. Take into consideration required consistency, reliability and high availability and you may realize that there are more suitable once. Rest API should not be the main driver, because you can always develop the API yourself, if not supported by given technology.
Pros of Azure Cosmos DB
- Best-of-breed NoSQL features28
- High scalability22
- Globally distributed15
- Automatic indexing over flexible json data model14
- Tunable consistency10
- Always on with 99.99% availability sla10
- Javascript language integrated transactions and queries7
- Predictable performance6
- High performance5
- Analytics Store5
- Rapid Development2
- No Sql2
- Auto Indexing2
- Ease of use2
Pros of Cassandra
- Distributed118
- High performance97
- High availability81
- Easy scalability74
- Replication52
- Reliable26
- Multi datacenter deployments26
- Schema optional10
- OLTP9
- Open source8
- Workload separation (via MDC)2
- Fast1
Sign up to add or upvote prosMake informed product decisions
Cons of Azure Cosmos DB
- Pricing17
- Poor No SQL query support4
Cons of Cassandra
- Reliability of replication3
- Size1
- Updates1