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

Microsoft Azure Cosmos DB vs ScyllaDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Apr 6, 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

Microsoft Azure Cosmos DB
Ranking in NoSQL Databases
3rd
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
89
Ranking in other categories
Database as a Service (DBaaS) (6th), Managed NoSQL Databases (1st), Vector Databases (3rd)
ScyllaDB
Ranking in NoSQL Databases
2nd
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
12
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the NoSQL Databases category, the mindshare of Microsoft Azure Cosmos DB is 3.3%. The mindshare of ScyllaDB is 10.3%, up from 9.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases
 

Featured Reviews

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.
ArpitShah - PeerSpot reviewer
Self-hosting complexity and the way ScyllaDB counts operations can be confusing and may not reflect actual usage
It seems we have better options available. So probably don't go for ScyllaDB. The reason is, first, it's very high. It's not as straightforward as, like, Postgres or ClickHouse to set up. It requires a complex setup. The other problem is what they call. For example, they will say that for up to a million operations, you experience this. But the problem is if they have nine servers, then your one operation is counted as nine operations, not one. So, even though you have one write, they count it as nine. It's like it's just not false premises. You can always host it yourself, but then it's way more complex. The benefits are not substantially more than those of other databases. It's not that it's slow or anything. It's good enough and all. But it's just that ClickHouse or other databases are simpler and faster and probably provide more features. So, I kind of burn out from the database, and that's why I would keep it small.

Quotes from Members

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

Pros

"Scaling the workloads is one of the key advantages of Cosmos, preventing the database from becoming a performance bottleneck."
"The solution is easy to use, and it is also easy to integrate with several things for database use cases."
"Microsoft Azure Cosmos DB is very easy to use."
"The querying language and the SDKs they've provided over the years have been phenomenal, giving us a significant advantage."
"It has been very efficient so far. The team has been using it for quite a while. I am new to the team, but they always talk about how efficient it is."
"It is a cloud-based solution that is easy to deploy, easy to access, and provides users with more features compared to other clouds like AWS and GCP."
"The product has a lot of useful features that are there and ready to use, it's also very easy to use."
"The best feature of Microsoft Azure Cosmos DB is API access, which makes it very easy to interact with the database without needing to write queries."
"The performance and scalability are good, and we hardly see any major issues with ScyllaDB."
"ScyllaDB is very fast, and I can use it for so many things."
"ScyllaDB allows fine-tuning of the table structure. Speed is probably the most critical factor because we perform a lot of heavy data ingestion. One of its core features is its ability to handle high volumes and maintain speed when accessing data. Additionally, high availability and partitioning are built-in features of ScyllaDB."
"The documentation is good. It integrates easily with our existing data infrastructure."
"I like how fast it is to query data from the ScyllaDB node!"
"The performance aspects of Scylla are good, as always... A good point about Scylla is that it can be used extensively."
"It is lightweight, and it requires less infrastructure."
"The best features of ScyllaDB are how it synchronizes data and its failover system. There's a unique formula to decide the number of nodes you need and the minimum required, which I find helpful. It also offers encryption and supports APIs, making it great for distributed systems and scaling databases across different regions. While it's easy to use, having prior experience helps configure it properly. There are many configurations; if you don't understand them, you might mess up the design. So, understanding your system's needs, like whether it requires more read or write operations, is crucial for setting up the correct configuration."
 

Cons

"It is easy to use, but optimization has been a mixed experience. It has been more of trying to figure out how to do so. We have not found much support there, so we have to come up with our own way of optimizing it in different ways. That is one area of improvement."
"The initial setup was difficult."
"For streaming platforms, Azure Cosmos DB could improve efficiency in data storage. Indexing can also be better. Enhanced capabilities are necessary to manage increased data amounts more effectively during searches."
"I had a challenging experience implementing the emulator with a Mac. I had to install the emulator in a Docker container because it is not natively compatible. A significant amount of time was spent researching how to enable HTTPS communication when connecting the container and the emulator."
"Because there is no local way of doing things, Azure Cosmos DB will always be considered expensive."
"The RUs still appear to be a black box for everyone. Even though they explain read and write RUs, it remains unclear for many users."
"One area of improvement for Cosmos database is the auto-scaling of RUs during high loads. It would be beneficial if the database could automatically scale resources rather than requiring manual adjustments."
"The current data analytics of Cosmos DB is inefficient for large-scale queries due to its transactional design."
"We faced several challenges while integrating ScyllaDB into our AWS environment. One common issue was that a security port wasn’t opened on one node, preventingdata synchronization across clusters. We noticed the data wasn’t syncing correctly when we saw different record counts in other regions. After investigating, we found that the port was closed in one AWS region. Once we opened the port, the data synchronization across all nodes resumed as expected."
"Data export, along with how we can purchase the data periodically, needs to be improved so that the storage is within control. Then, we could optimize it even better."
"It seems we have better options available. So probably don't go for ScyllaDB. The reason is, first, it's very high. It's not as straightforward as, like, Postgres or ClickHouse to set up. It requires a complex setup."
"ScyllaDB needs to improve its handling of transactions."
"The documentation of Scylla is an area with shortcomings and needs to be improved."
"Some of the regular commands in NoSQL do not work."
"The documentation is not well established for new developers."
"The product needs to add more features and improve the response time of the support team."
 

Pricing and Cost Advice

"Cosmos DB is expensive compared to any virtual machine based on conventional RDBMS like MySQL or PostgreSQL."
"Its pricing is higher compared to solutions like Aerospike. However, it is justified because of the out-of-the-box features that are provided. The availability and resiliency that we have make it worth the price."
"With heavy use, like a large-scale IoT implementation, you could easily hit a quarter of a million dollars a month in Azure charges if Cosmos DB is a big part of it."
"It is expensive. The moment you have high availability options and they are mixed with the type of multitenant architecture you use, the pricing is on the higher end."
"Microsoft Azure Cosmos DB is moderately priced, where it is neither expensive nor cheap."
"The RU's use case determines our license fees."
"Its pricing is not bad. It is good."
"The pricing for Cosmos DB has improved, particularly with the new pricing for Autoscale."
"I believe that there is a yearly licensing cost and that it's expensive."
"It's a bit expensive."
"It is an expensive tool compared to its competitor."
"It's free."
"The paid version of ScyllaDB is not that expensive. The main advantage of the paid version is direct support from the ScyllaDB team, which can resolve issues faster—typically within a day, compared to two to three days with the free version. The paid version also offers better guidance and support, while the free version has good documentation and is more high-level. I’d rate their support team nine out of ten because of the quick responses from their community."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Legal Firm
12%
Computer Software Company
11%
Comms Service Provider
11%
Financial Services Firm
10%
Computer Software Company
17%
Financial Services Firm
13%
Comms Service Provider
8%
Hospitality Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 cost is transparent. Pricing depends on the transaction and data size, but overall, it is cheaper compared to hosting it on your corporate network due to other factors like power consumption. C...
What needs improvement with Microsoft Azure Cosmos DB?
I had a challenging experience implementing the emulator with a Mac. I had to install the emulator in a Docker container because it is not natively compatible. A significant amount of time was spen...
What do you like most about Scylla?
The performance aspects of Scylla are good, as always... A good point about Scylla is that it can be used extensively.
What is your experience regarding pricing and costs for Scylla?
The enterprise version comes with a cost of about $300,000 per year, however, we did not experience the promised compaction benefits.
What needs improvement with Scylla?
From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction. Additionally, ticketing and support systems could be improved due to the time it takes to get answers. T...
 

Also Known As

Microsoft Azure DocumentDB, MS Azure Cosmos DB
No data available
 

Overview

 

Sample Customers

TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
IBM, Investing.com, mParticle, Comcast, GE, Fanatics, Ola, CERN, adgear, Samsung
Find out what your peers are saying about Microsoft Azure Cosmos DB vs. ScyllaDB and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.