Cassandra vs Azure Cosmos DB

• Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
• Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
• Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
• Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.

Read full review

• Turn-key geo-redundancy with multi-master writes is unprecedented and unparalleled in the industry!
• Guaranteed low latency makes Cosmos DB an excellent fit for most of our performance-intensive situations.
• The tunable consistency model simplifies so many challenges in distributed systems engineering that otherwise require advanced knowledge of computer science topics. I continue to be impressed at how Cosmos DB has abstracted away so much complexity.

Read full review

• Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
• Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
• There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.

Read full review

• Expensive, so be careful of the use case.
• We had a thought time migrating from traditional DBs to Cosmos. Azure should provide a seamless platform for the migration of data from on-premises to cloud.

Read full review

• I have no experience with this but from the blogs and news what I believe is that in businesses where there is high demand for scalability, Cassandra is a good choice to go for.
• Since it works on CQL, it is quite familiar with SQL in understanding therefore it does not prevent a new employee to start in learning and having the Cassandra experience at an industrial level.

Read full review

• Azure Cosmos DB may be expensive on its own, but it was cheaper than increasing the size/power of our VMs running SQL Server instances enough to keep up with the volume and velocity of the unstructured data.
• We got the JSON data out of our SQL Servers and they quit tipping over.

Read full review