Try our new research platform with insights from 80,000+ expert users

Cassandra vs Microsoft Azure Cosmos DB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 5, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Cassandra
Ranking in NoSQL Databases
4th
Ranking in Vector Databases
15th
Average Rating
8.0
Reviews Sentiment
6.1
Number of Reviews
23
Ranking in other categories
No ranking in other categories
Microsoft Azure Cosmos DB
Ranking in NoSQL Databases
3rd
Ranking in Vector Databases
3rd
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
85
Ranking in other categories
Database as a Service (DBaaS) (6th), Managed NoSQL Databases (1st)
 

Mindshare comparison

As of April 2025, in the NoSQL Databases category, the mindshare of Cassandra is 10.8%, down from 12.8% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 2.9%. It is calculated based on PeerSpot user engagement data.
NoSQL Databases
 

Featured Reviews

Himanshu Amodwala - PeerSpot reviewer
Well-equipped to handle a massive influx of data and billions of requests
The use of Cassandra in real-time data analytics has been pivotal for our e-commerce platform. As our platform operates 24/7, providing services to sellers and customers alike, the need for real-time updates is paramount. For instance, when a customer leaves comments or feedback on an image, they anticipate an immediate reflection of these changes on the portal. Similarly, sellers altering product attributes or updating images expect instant visibility of these modifications. Handling large data volumes with Cassandra has been an excellent experience. Despite challenges related to the influx, these were not attributed to Cassandra itself but rather to middle-layer issues. Generally, it demonstrated scalability with workloads, thanks to its horizontal scaling capabilities. We could easily add new nodes to the system as needed, ensuring the platform coped well with increasing loads. The tool's most beneficial feature for scalability is its entire architecture. The absence of a single point of failure or a leader within the ecosystem contributes to its robust scalability. This key aspect influenced our decision to opt for the Cassandra ecosystem. In terms of performance, it demonstrated the ability to handle approximately 1.6 billion requests per day. This was achieved on AWS using EC2 instances, and it was during a period about four to five years ago.
MichaelJohn - PeerSpot reviewer
Very efficient for application-facing scenarios
There are several areas for improvement. Firstly, having a local development emulator or simulator for Azure Cosmos DB would be beneficial. It would be very handy to have a Docker container that developers can use locally. Although, I know there is a free tier and so on and so forth, having a local environment would be nice. For example, SQL Server is very portable. You can even install it on your machine. That is the number one thing that is missing in Azure Cosmos DB. The second improvement area is the IDE of choice. That means how you interact with Azure Cosmos DB. For example, with SQL Server, you have SQL Server Management Studio. I know there is a little bit of support for Azure Cosmos DB in Azure Data Studio, but it is not heavily advertised or it does not feel like first-class citizen support. Developer experience or developer tooling is missing in terms of interacting with the database. Better developer tools or an IDE for interacting with Azure Cosmos DB would enhance the developer experience. Lastly, there is some mixed messaging about what Azure Cosmos DB is, given its multiple APIs. There are so many Azure Cosmos DB APIs available. There is NoSQL. There are MongoDB, Gremlin, and others. There is still some mixed messaging for others who are new to Azure Cosmos DB about what Azure Cosmos DB is. Is this like MongoDB, but then there is also MongoDB in Azure Cosmos DB? I know it well, and I know that the default one is just NoSQL, but others I have interacted with over the last ten years or so get confused.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable features of this solution are its speed and distributed nature."
"Can achieve continuous data without a single downtime because of node to node ring architecture."
"A consistent solution."
"Its retrieval is similar to an RDBMS, so our team finds it easy to adapt."
"Some of the valued features of this solution are it has good performance and failover."
"Cassandra has some features that are more useful for specific use cases where you have time series where you have huge amounts of writes. That should be quick, but not specifically the reads. We needed to have quicker reads and writes and this is why we are using Cassandra right now."
"We can add almost one million columns to the solution."
"Our primary use case for the solution is testing."
"The most valuable features of Microsoft Azure Cosmos DB were the general infrastructure, ease to use, and interface."
"I truly recommend Cosmos DB because it is a serverless product."
"Since it's a managed service, Azure backend handles scalability. From a user's perspective, we don't need to worry about scalability."
"I would rate it a ten out of ten for stability."
"Our team has found the vCore index to be one of the most valuable features. We have tokenized and vectorized our entire database and stored this data in MongoDB collections with a vCore index, which works like magic for keyword selection."
"It's highly scalable and supports consistency, security, and multiple security options."
"Cosmos DB makes life easier because if we want to use Mongo-type data, or Cassandra-type data, or maybe even just a simple cable storage-type data, then graph, there are multiple ways to do this."
"Azure Cosmos DB's resiliency is valuable. It is available in every Azure region, allowing quick information storage and retrieval. We can partition it to improve indexing, enabling us to retrieve information and recreate website content quickly."
 

Cons

"We found some issues with the batch inserts when the data volume is large."
"Fine-tuning was a bit of a challenge."
"There could be more integration, and it could be more user-friendly."
"There were challenges with the query language and the development interface. The query language, in particular, could be improved for better optimization. These challenges were encountered while using the Java SDK."
"The solution is not easy to use because it is a big database and you have to learn the interface. This is the case though in most of these solutions."
"I want Cassandra to update its open-source version more quickly. It's already feature-rich, but I'd appreciate better integration with other NoSQL databases like MariaDB or MongoDB. If I ever need to work with customers or vendors using different NoSQL databases, having native integration in Cassandra would make managing and interacting with their databases much easier."
"Cassandra can improve by adding more built-in tools. For example, if you want to do some maintenance activities in the cluster, we have to depend on third-party tools. Having these tools build-in would be e benefit."
"It can be difficult to analyze what's going on inside of the database relative to other databases. It can also be difficult to troubleshoot sometimes."
"There are multiple approaches to implementing multitenant architecture on Azure Cosmos DB, but there is still no single or best-recommended approach when you have a big variance in the size of your tenants. That is something that still needs to be worked on."
"In the long run, there should be an addition of more features, especially because this space is evolving quickly. It all boils down to how many more features you are adding, how many integrations you are supporting, and how many more APIs you have that are standard APIs."
"We should have more freedom to tweak it and make our own queries for non-traditional use-cases."
"The query is a little complex. SQL server should have more options. But the query should be better."
"One of our biggest pain points is the backup and restore functionality needs improvement. They've gotten a little better in this area. SQL Server's long-term retention is amazing, and you can restore data from years ago. You need to open a support Microsoft ticket to restore your Cosmos DB backup, and it comes in on a different Cosmos account. It's just kind of a headache to restore data."
"Sometimes, the solution's access request takes time, which should be improved."
"The auto-scaling feature adjusts hourly. We have many processes that write stuff in batches, so we must ensure that the load is spread evenly throughout the hour. It would be much easier if it were done by the minute. I'm looking forward to the vector database search that they are adding. It's a pretty cool new feature."
"The query searching functionality has some complexities and could be more user-friendly. Improvements in this area would be very helpful."
 

Pricing and Cost Advice

"I don't have the specific numbers on pricing, but it was fairly priced."
"I use the tool's open-source version."
"We are using the open-source version of Cassandra, the solution is free."
"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."
"We pay for a license."
"There are licensing fees that must be paid, but I'm not sure if they are paid monthly or yearly."
"The pricing for Microsoft Azure Cosmos DB is good. Initially, it seemed like an expensive way to manage a NoSQL data store, but so many improvements that have been made to the platform have made it cost-effective."
"I would rate Cosmos DB's cost at seven out of ten, with ten being the highest."
"Pricing is mid- to high-end."
"The price of Microsoft Azure Cosmos DB could be a bit lower."
"Cosmos DB is a managed offering, so its cost is understandably higher."
"The cost is the biggest limitation of this solution."
"The RU's use case determines our license fees."
"Cosmos DB is expensive, and the RU-based pricing model is confusing. Although they have a serverless layer, there are deficiencies in what I can define and assign to a database. Estimating infrastructure needs is not straightforward, making it challenging to manage costs."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
15%
Healthcare Company
5%
Manufacturing Company
5%
Legal Firm
12%
Computer Software Company
11%
Comms Service Provider
11%
Financial Services Firm
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Cassandra?
The use of Cassandra in real-time data analytics has been pivotal for our e-commerce platform. As our platform operates 24/7, providing services to sellers and customers alike, the need for real-ti...
What needs improvement with Cassandra?
Cassandra is very complex to manage. Sometimes, I need to involve a senior DevOps engineer if we encounter a problem. About a year ago, we were unable to recover data without help from a senior Dev...
What do you like most about Microsoft Azure Cosmos DB?
The initial setup is simple and straightforward. You can set up a Cosmos DB in a day, even configuring things like availability zones around the world.
What is your experience regarding pricing and costs for Microsoft Azure Cosmos DB?
Its pricing is not bad. It is good. We have a contract with Microsoft to use their technology. In my opinion, Microsoft Azure Cosmos DB is a good option for the total cost of ownership.
What needs improvement with Microsoft Azure Cosmos DB?
I think Cosmos DB enhanced the benefits of NoSQL databases, offering query flexibility, partition management, and backup and restore options. These aspects are crucial, and perhaps improving the co...
 

Also Known As

No data available
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Overview

 

Sample Customers

1. Apple 2. Netflix 3. Facebook 4. Instagram 5. Twitter 6. eBay 7. Spotify 8. Uber 9. Airbnb 10. Adobe 11. Cisco 12. IBM 13. Microsoft 14. Yahoo 15. Reddit 16. Pinterest 17. Salesforce 18. LinkedIn 19. Hulu 20. Airbnb 21. Walmart 22. Target 23. Sony 24. Intel 25. Cisco 26. HP 27. Oracle 28. SAP 29. GE 30. Siemens 31. Volkswagen 32. Toyota
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about Cassandra vs. Microsoft Azure Cosmos DB and other solutions. Updated: February 2025.
845,406 professionals have used our research since 2012.