No more typing reviews! Try our Samantha, our new voice AI agent.

Microsoft Azure Cosmos DB vs ScyllaDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 25, 2026

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
1st
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
110
Ranking in other categories
Database as a Service (DBaaS) (3rd), Managed NoSQL Databases (1st), Vector Databases (1st)
ScyllaDB
Ranking in NoSQL Databases
7th
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 August 2026, in the NoSQL Databases category, the mindshare of Microsoft Azure Cosmos DB is 6.0%, up from 5.1% compared to the previous year. The mindshare of ScyllaDB is 5.9%, down from 10.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Microsoft Azure Cosmos DB6.0%
ScyllaDB5.9%
Other88.1%
NoSQL Databases
 

Featured Reviews

Michael Hasenfang - PeerSpot reviewer
Director, Platform Engineering - Infrastructure Systems and Automation at a computer software company with 1,001-5,000 employees
Collecting compliance data has become more efficient while managing unstructured inputs for reporting
The features that I find most valuable within Microsoft Azure Cosmos DB are probably the cost, as the cost optimization is good. The storage and queryability are good for what we're doing; it's a lot of unstructured data, so having a platform to put that in and then be able to harvest that data out for the reporting we do is essential. In terms of cost saving, it was probably easily 30 to 40% cheaper than doing a standard SQL, which is what we saw just on piloting and getting in there. We were initially thinking 20 to 25%, but we were probably more at the 35 to 40%. We are using Microsoft Azure Cosmos DB's hybrid search today. The value that it has added to my AI or search workloads is that I think it's optimized that process and made it easier. We have a lot of unstructured data coming from different dissimilar systems and different data sources, so correlating those things together and making sense of it has been very beneficial. Microsoft Azure Cosmos DB has had pretty good performance with searching through large amounts of data; it's been fast, and we haven't seen a lot of performance degradation while building larger queries and bringing in a large set of data. The dynamic auto-scale or serverless model from Microsoft Azure Cosmos DB has helped reduce costs and operational effort; however, it's hard to quantify how that plays out since you're using a shared service. It shifts my focus away from building, managing, and upgrading to adding value.
Manikandan Gunasekaran - PeerSpot reviewer
Director of Engineering at Ola
Reliable data management with great reliability and performance
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. There's also an issue with compatibility when attempting to switch back from the enterprise to the community version.

Quotes from Members

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

Pros

"It handles large-scale operations efficiently, such as tracking views, logs, or events."
"It gives us a lot of flexibility. The scaling is instantaneous as well. You immediately have all the resources available."
"Microsoft Azure Cosmos DB's most valuable feature is latency."
"The best features of Microsoft Azure Cosmos DB include the speed to query data; as long as you index properly, retrieving data is fast and lightweight."
"I truly recommend Cosmos DB because it is a serverless product."
"It's not a specific feature that I value, but the scalability of this system is the most impressive aspect."
"I would recommend Microsoft Azure Cosmos DB to other users without hesitation."
"I would rate Microsoft Azure Cosmos DB a ten out of ten."
"The performance and scalability are good, and we hardly see any major issues with ScyllaDB."
"The documentation is good. It integrates easily with our existing data infrastructure."
"The product's most valuable features are efficiency and reliability."
"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."
"ScyllaDB is fast and reliable. It has good performance."
"ScyllaDB is very fast, and I can use it for so many things."
"The performance aspects of Scylla are good, as always... A good point about Scylla is that it can be used extensively."
"I like how fast it is to query data from the ScyllaDB node!"
 

Cons

"The challenge for us is always scale."
"Our use case was a failure with Microsoft Azure Cosmos DB, and we do not have any other opportunity to use Microsoft Azure Cosmos DB."
"There were instances where the DB was not responding, and we lost some part of our business due to that."
"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."
"In that scenario, two things can be improved."
"I don't think Cosmos DB has improved our organization. People are using it, but I'm not sure it's the best solution. For one, it's costly. Also, there are other issues with it. You cannot get all the records simultaneously. You can only get it in chunks of 1,500 maximum."
"One area for improvement is the ease of writing SQL queries and stored procedures in Microsoft Azure Cosmos DB. Writing an SQL query and a stored procedure on top of that is a little challenging."
"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."
"Support and the availability of support need improvement. I would give them a six out of ten."
"We've had occasional performance challenges that required resource adjustments or optimizations in our interaction with the platform."
"ScyllaDB needs to improve its handling of transactions."
"If you don't have the best computing resources, then it's not easy to set up. In such cases, we have to run ScyllaDB in developer mode."
"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."
"Some of the regular commands in NoSQL do not work."
"From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction."
"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."
 

Pricing and Cost Advice

"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."
"Cosmos DB gave us three accounts for $400. We pay according to the usage."
"The pricing and licensing model was initially difficult to understand, but as soon as I learned what was going on and how it was priced, it was pretty easy."
"Its price is very good for the basic stuff. When you go to a more complicated use case, especially when you need replication and availability zones, it gets a little costly."
"The solution is very expensive."
"The tool is not expensive."
"The RU's use case determines our license fees."
"We are not consuming so much yet since we are at the beginning of using this solution. I would rate the pricing of Microsoft Azure Cosmos DB a six out of ten."
"It is an expensive tool compared to its competitor."
"It's free."
"I believe that there is a yearly licensing cost and that it's expensive."
"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."
"It's a bit expensive."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Legal Firm
11%
Comms Service Provider
8%
Manufacturing Company
8%
Outsourcing Company
14%
Comms Service Provider
9%
Financial Services Firm
8%
Transportation Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise24
Large Enterprise58
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise8
 

Questions from the Community

What is your experience regarding pricing and costs for Microsoft Azure Cosmos DB?
Microsoft Azure Cosmos DB's pricing model has aligned with my budget expectations because I can tune the RU as I need to, which helps a lot. Microsoft Azure Cosmos DB's dynamic auto-scale or server...
What needs improvement with Microsoft Azure Cosmos DB?
I have not utilized Microsoft Azure Cosmos DB multi-model support for handling diverse data types. I'm not in the position to decide if clients will use Microsoft Azure Cosmos DB or any other datab...
What is your primary use case for Microsoft Azure Cosmos DB?
We have a very large team of developers who develop a solution for our customers. In the part where they need some infrastructure on Microsoft Azure, we deploy entire environments of different type...
What is your experience regarding pricing and costs for Scylla?
From what I’ve seen (and experienced), ScyllaDB pricing is very dependent on how you deploy it, and that’s where most of the confusion comes from.
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...
What is your primary use case for Scylla?
We dump a lot of our data, such as every entry created with respect to when a user rides a scooter, every record gets updated to ScyllaDB. It is used as a single source of truth and it manages mass...
 

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: August 2026.
909,725 professionals have used our research since 2012.