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

Amazon DocumentDB vs Microsoft Azure Cosmos DB 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

Amazon DocumentDB
Ranking in Managed NoSQL Databases
5th
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Microsoft Azure Cosmos DB
Ranking in Managed NoSQL Databases
1st
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
91
Ranking in other categories
Database as a Service (DBaaS) (6th), NoSQL Databases (3rd), Vector Databases (3rd)
 

Mindshare comparison

As of May 2025, in the Managed NoSQL Databases category, the mindshare of Amazon DocumentDB is 10.0%, down from 13.7% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 15.4%, down from 18.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases
 

Featured Reviews

Javed Zahoor - PeerSpot reviewer
Offers the ability to replicate data across different instances
Its speed has had the most significant impact on our projects. For starters, we used it for its flexibility. With DocumentDB, you're not tied to a rigid structure like you are with Aurora or other relational databases. This makes it great for startups. When we work with established systems where the structure is well-defined, the speed of DocumentDB becomes the most important factor. Compared to a relational database, scaling DocumentDB is easier because of its ability to replicate data across different instances. If you use a network-based storage service with your cluster, the primary instance doesn't even need a full local copy of the data, since it's accessible on the shared storage. That definitely contributes to scalability. AWS-managed services already handle a lot of the scaling complexity. We don't have to do anything.
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

"Migrations are easy using this product."
"Amazon DocumentDB is a simple solution."
"Its speed has had the most significant impact on our projects. For starters, we used it for its flexibility. With DocumentDB, you're not tied to a rigid structure like you are with Aurora or other relational databases. This makes it great for startups."
"The solution is used because we get faster response times with large data sets than with SQL. It's essential for us because we have half a billion rows, and we need to return them quickly."
"It is integral to our business because it helps manage schema and metadata for all our documents and customers. The AI insights we glean based on Azure OpenAI also end up in Cosmos DB. We need a NoSQL store because the schema is dynamic and flexible, so Cosmos DB is a great fit. It has four nines or possibly five nines availability, excellent geo-distribution, and auto-scaling."
"Azure Cosmos DB helped improve the quality of our search results."
"The most valuable feature of the solution is that it is scalable with multiple master files."
"Cosmos DB is effective at handling large queries."
"The speed is impressive, and integrating our power-up database with Kafka was an improvement."
"Azure Cosmos DB offers numerous data connectors that provide a platform for seamless integration with various platforms and visualization tools such as Power BI. It allows connection via multiple data connectors to integrate data in any desired format."
"Our customer is very satisfied with it."
 

Cons

"The technical support could be improved."
"There's a bit of a learning curve at the beginning."
"One possible improvement could be a hybrid database solution, where parts of the application leverage a relational database alongside DocumentDB. If a system were heavily relational in nature, a database like PostgreSQL might be a good fit."
"The one thing that I have been working on with Microsoft with regard to this is the ability to easily split partitions and have it do high-performance cross-partition queries. That is the only place where either our data size or our throughput has grown beyond one partition, so being able to do cross-partition queries efficiently would be my number one request."
"Microsoft Azure Cosmos DB's performance could be better. In large volumes of documents, the querying process becomes slow and complicated."
"One of the primary challenges with Cosmos DB as a non-relational data store is the careful data modeling required due to the lack of collection-level joins when using the SQL API."
"Slight enhancements in integration interfaces, expanded dashboard functionalities, and broader use-case support would be beneficial."
"Microsoft's support services are inadequate, especially during critical incidents."
"Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand."
"Azure Cosmos DB could be better for business intelligence and analytical queries."
"There is room for improvement in terms of stability."
 

Pricing and Cost Advice

Information not available
"The pricing for Cosmos DB has improved, particularly with the new pricing for Autoscale."
"The solution is very expensive."
"It is cost-efficient as long as you understand the right setup to optimize usage. Knowing the data needs of the organization and adjusting the Microsoft Azure Cosmos DB usage accordingly helps save costs, but if you don't know, you could end up spending more than necessary."
"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."
"Azure Cosmos DB's pricing is competitive, though there is a need for more personalized pricing models to accommodate small applications without incurring high charges. A suggestion is to implement dynamically adjustable pricing that accounts for various user needs."
"The tool is not expensive."
"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."
"Microsoft Azure Cosmos DB pricing is based on RUs. Reading 1 KB document costs one RU, whereas writing one document costs five RUs. Pricing for querying depends on the complexity of the query. If you increase the document size, it will automatically increase the RU cost."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
16%
Manufacturing Company
12%
Government
7%
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
No data available
 

Questions from the Community

What advice do you have for others considering Amazon DocumentDB?
Amazon DocumentDB offers us many useful features. It is definitely a solution that an organization in need of comprehensive and effective document management should invest its money into. We are im...
What do you like most about Amazon DocumentDB?
Its speed has had the most significant impact on our projects. For starters, we used it for its flexibility. With DocumentDB, you're not tied to a rigid structure like you are with Aurora or other ...
What is your experience regarding pricing and costs for Amazon DocumentDB?
The specific DocumentDB implementation we use is on the expensive side. We tend to use it strategically in complex systems, primarily for lookup capabilities. For simpler use cases, we often choose...
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?
It is cost-efficient as long as you understand the right setup to optimize usage. Knowing the data needs of the organization and adjusting the Microsoft Azure Cosmos DB usage accordingly helps save...
What needs improvement with Microsoft Azure Cosmos DB?
What is missing in Microsoft Azure Cosmos DB is definitely cold storage. We know it's coming, but that's currently what is missing—the possibility to park older data in a cold tier. Aside from the ...
 

Also Known As

No data available
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Overview

 

Sample Customers

Finra, The Washington Post, Freshop
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about Amazon DocumentDB vs. Microsoft Azure Cosmos DB and other solutions. Updated: April 2025.
851,604 professionals have used our research since 2012.