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

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

Amazon DocumentDB
Ranking in Managed NoSQL Databases
9th
Average Rating
8.2
Reviews Sentiment
4.0
Number of Reviews
6
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
6.9
Number of Reviews
109
Ranking in other categories
Database as a Service (DBaaS) (4th), NoSQL Databases (2nd), Vector Databases (1st)
 

Mindshare comparison

As of May 2026, in the Managed NoSQL Databases category, the mindshare of Amazon DocumentDB is 6.5%, down from 9.6% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 15.7%, down from 16.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Microsoft Azure Cosmos DB15.7%
Amazon DocumentDB6.5%
Other77.8%
Managed NoSQL Databases
 

Featured Reviews

Hemanth Perepi - PeerSpot reviewer
Technical Lead at Trianz
Supports high-level data management and secure migration
Over the past few months, I’ve been working closely with a managed database service, and a few features stood out as game changers for me and my team: MongoDB Compatibility – The seamless migration experience was a huge win. No need to rewrite code or change drivers, which meant less friction and faster adoption for our developers. Fully Managed Service – Patching, backups, and monitoring are all automated. This freed up our team to focus on building applications instead of managing infrastructure. Separation of Compute & Storage – The flexibility to scale compute and storage independently gave us both cost savings and better performance optimization. Multi-AZ High Availability – Automatic failover and cross-AZ replication gave us peace of mind with improved uptime and disaster recovery. Performance at Scale – Even with large datasets, performance has remained consistent. Read replicas and efficient indexing have been especially valuable for read-heavy workloads. Security – End-to-end encryption, VPC isolation, and IAM integration made enterprise-level security feel straightforward and reliable. Backup & Recovery – Point-in-time recovery with automated backups made data protection effortless.
reviewer2724105 - PeerSpot reviewer
Senior Director of Product Management at a tech vendor with 1,001-5,000 employees
Provides super sharp latency, excellent availability, and the ability to effectively manage costs across different tenants
For integrating Microsoft Azure Cosmos DB with other Azure products or other products, there are a couple of challenges with the current system. Right now, the vectors are stored as floating-point numbers within the NoSQL document, which makes them inefficiently large. This leads to increased storage space requirements, and searching through a vast number of documents in the vector database becomes quite costly in terms of RUs. While the integration works well, the expense associated with it is relatively high. I would really like to see a reduction in costs for their vector search, as it is currently on the expensive side. The areas for improvement in Microsoft Azure Cosmos DB are vector pricing and vector indexing patterns, which are unintuitive and not well described. I would also like to see the parameters of Fleet Spaces made more powerful, as currently, it's somewhat lightweight. I believe they've made those changes intentionally to better understand the cost model. However, we would like to take a more aggressive approach in using it. One of the most frustrating aspects of Microsoft Azure Cosmos DB right now is that you can only store one vector per document. Additionally, you must specify the configuration of that vector when you create an instance of Microsoft Azure Cosmos DB. Once the database is set up, you can't change the vector configuration, which is incredibly limiting for experimentation. You want the ability to try different settings and see how they perform, as there are numerous use cases for storing more than one vector in a document. While interoperability within the vector database is acceptable—for example, I can search for vectors—I still desire a richer set of configuration options.

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."
"Efficient data retrieval with millisecond fetch times sets it apart from RDS."
"The product is fast and easy to use."
"Efficient data retrieval with millisecond fetch times sets it apart from RDS."
"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."
"There are many benefits to using Amazon DocumentDB, for example, regarding the price, you can start with a small database and when you need more performance, you can grow the database."
"Amazon DocumentDB is a simple solution."
"I would recommend Cosmos. It made our lives a lot easier. There's not a big learning curve in order to understand the structure and how to use it."
"What I like about Microsoft Azure Cosmos DB is that it's easy to do data ingestion and use the data in different applications."
"The features most valuable to us in Microsoft Azure Cosmos DB are the auto scale and change feed. These features allow us to do some operations that are not possible with SQL Server."
"The best feature of Microsoft Azure Cosmos DB is the replication all over the world."
"The most valuable feature of Microsoft Azure Cosmos DB is its ability to handle concurrency and consistency."
"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."
"The solution is scalable, and we intend to increase our usage."
"The high speed of Azure Cosmos DB compared to other competitors is remarkable."
 

Cons

"However, when you need more volume or more registers, it becomes complicated because the performance adjustments and tuning are challenging."
"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."
"Improvements for Amazon DocumentDB could focus on enhancing high availability, sharding methods, replication techniques, and automatic failover in case the primary goes down, as continuous backup is an excellent option for disaster recovery."
"The technical support could be improved."
"There's a bit of a learning curve at the beginning."
"Improvements for Amazon DocumentDB could focus on enhancing high availability, sharding methods, replication techniques, and automatic failover in case the primary goes down, as continuous backup is an excellent option for disaster recovery."
"There's a bit of a learning curve at the beginning."
"There are no specific areas I believe need improvement as I am happy with what I am getting currently. However, I am open to new features in future versions, like possibly integrating AI features natively into Cosmos DB. Any improvement would be beneficial."
"The current data analytics of Cosmos DB is inefficient for large-scale queries due to its transactional design."
"Customer service and technical support from Microsoft have been all right. On a scale of 1 to 10, I would give them probably a six, maybe a hard seven at most."
"Continuing to educate customers on how they can take better advantage of Microsoft Azure Cosmos DB without having to completely rewrite their entire application paradigm would be beneficial. They can help them understand that there are multiple options to interact with it. They do not necessarily have to start from scratch. They can refactor their existing application to be able to use it better."
"A minor improvement would be enabling batch operations through the UI. Currently, to delete all documents in a collection, we must use an API, which some of my team finds inconvenient for admin tasks."
"The cost is a concern. Microsoft Azure Cosmos DB did not decrease our total cost of ownership. From the standpoint of the old way of doing DBA operations, it did, but our cloud cost increased significantly."
"It would be ideal if we could integrate Cosmos DB with our Databricks. At this point, that's not possible."
"An improvement would be a more robust functionality around updating elements on a document, or some type of procedural updates that don't require pulling the entire document."
 

Pricing and Cost Advice

Information not available
"Azure is a pay as you go subscription."
"Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high."
"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."
"Cosmos DB is cost-effective when starting but requires careful management."
"The solution is very expensive."
"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."
"This cost model is beneficial because it allows for cost control by limiting resource units (RUs), which is ideal. However, for our needs, we can't engage with their minimum pricing, which ranges from 100 to 1,000 RUs. At the bare minimum, we need to use 4,000 RUs for a customer. I would like to find a way to gain some advantages from the lowest tier, particularly the ability to scale down if necessary. It would be helpful to have more flexibility in cost management at the lower end."
"Microsoft Azure Cosmos DB's licensing costs are monthly."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
894,668 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Financial Services Firm
11%
Manufacturing Company
11%
Educational Organization
7%
Financial Services Firm
12%
Legal Firm
11%
Comms Service Provider
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise22
Large Enterprise58
 

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 is your experience regarding pricing and costs for Amazon DocumentDB?
The pricing and licensing of Amazon DocumentDB is managed directly by the client team with the vendor, so I am not involved in that aspect.
What needs improvement with Amazon DocumentDB?
We do not utilize Amazon DocumentDB's compatibility with MongoDB APIs because we do not have MongoDB in this client environment. There are current discussions about phasing out from AWS's Amazon Do...
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...
 

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 2026.
894,668 professionals have used our research since 2012.