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 Sep 29, 2024
 

Categories and Ranking

Amazon DocumentDB
Ranking in Managed NoSQL Databases
5th
Average Rating
8.4
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.3
Number of Reviews
76
Ranking in other categories
Database as a Service (DBaaS) (6th), NoSQL Databases (3rd), Vector Databases (5th)
 

Mindshare comparison

As of December 2024, in the Managed NoSQL Databases category, the mindshare of Amazon DocumentDB is 10.7%, down from 14.6% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 17.8%, down from 19.8% 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.
Michael Calvin - PeerSpot reviewer
Easy to integrate, has a shallow learning curve, and scales dynamically
Azure Cosmos DB is quick to adopt with a shallow learning curve. The average user can be operational within hours or days, handling small to medium data volumes. However, optimizing for ultra-high throughput scenarios involves a steeper learning curve, requiring substantial knowledge to master Azure Cosmos DB. Nonetheless, most users can leverage it as their operational data store with minimal effort. Our platform boasts several extensive language model features, particularly around summarization capabilities. We use vector searching in Azure Cosmos DB to facilitate the retrieval of an augmented generation model with our LLM implementation. It's a standard RAG implementation using Azure Cosmos DB. Compared to other options, a key advantage of vector indexing in Azure Cosmos DB is the ability to query documents alongside vectors. This pinpoints the precise information required for RAG in our LLM solution, granting us greater flexibility than vector searching in other Azure services. We integrated the vector database with the Azure OpenAI service for our LLM solution. The Azure AI services were simple to integrate with the vector database. There was a slight learning curve, especially as we were on the private preview of vector searching. This led to some hiccups with our existing database configurations, specifically regarding continuous backup. We couldn't enable continuous backup and vector searching simultaneously. However, this was solely due to our participation in the preview, and I'm confident this issue won't persist in the general availability release. Azure Cosmos DB is fantastic for searching large amounts of data when the data is within a single partition. Over the last two weekends, we ingested over 400 gigabytes of data into our Azure Cosmos DB database and saw no change in querying performance compared to when our database was only 20 gigabytes in size. This is impressive and powerful, but the scope is limited to those partition queries. The first benefit we've seen is increased developer productivity. Azure Cosmos DB is an easy database to work with. Its schema-less nature allows us to iterate quickly on our platform, develop new features, and store the associated data in Azure. Developers find it easy to use, eliminating the need for object-relational mapping tools and other overhead. Geographic replication and the ability to scale geographically is another advantage. This is challenging with other databases, even other NoSQL databases, but Azure Cosmos DB makes it easy. Cost optimization is a major benefit as well. We've been able to run our platform at a fraction of the infrastructure cost our customers incur when integrating with us. This allows us to focus resources on feature development and platform building rather than infrastructure maintenance. Azure Cosmos DB helped reduce the total cost of ownership. We don't need DBAs, system administrators, or typical IT staff to run the infrastructure because we can use Azure Cosmos DB as a platform or a software-as-a-service data storage solution. This makes the total cost of ownership significantly lower than any comparable solution using relational databases or other NoSQL solutions like MongoDB. We enable auto-scaling on all of our Azure Cosmos DB resources, which helps us achieve cost optimizations.

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."
"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."
"Amazon DocumentDB is a simple solution."
"The graphical representation of data is the most valuable feature of the solution."
"The most valuable feature of Microsoft Azure Cosmos DB is its ability to handle concurrency and consistency."
"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."
"Change notification works well, and the ability to process documents in a scalable way is important. This means we can efficiently thread out different operations and meet our organizational performance and scalability needs."
"It's highly scalable and supports consistency, security, and multiple security options."
"Microsoft Azure Cosmos DB offers the response times needed for advanced analytics applications."
"Cosmos DB is stable and easy to use."
"It is easy to use because you don't need to know much about Cosmos DB or have prior experience."
 

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."
"Once you create a database, it calls the container, and then items show up. A better description and more guidance would help because the first time I created it, I didn't understand that a container is similar to a table in SQL."
"The main area of improvement is the cost, as the expense is high. Also, when writing processes into Cosmos, sometimes the threshold is met, which can be a problem if developers have not written the code properly, limiting calls to five thousand."
"It would be beneficial if Cosmos supported batch and real-time use cases to make the system more seamless."
"In that scenario, two things can be improved."
"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."
"The support tickets are not cheap."
"We would like to see advancements in AI with the ability to benchmark vector search capabilities, ensuring it answers questions accurately. During our initial implementation, we faced challenges with indexing and sorting, which are natively available in other offerings but required specific configurations in Cosmos."
"The customer service is lacking. We have a premier support agreement, but support is hit and miss."
 

Pricing and Cost Advice

Information not available
"Cosmos DB is a managed offering, so its cost is understandably higher."
"The solution is very expensive."
"Microsoft Azure Cosmos DB's licensing costs are monthly."
"From a startup point of view, it appears to be expensive. If I were to create my startup, it would not have the pricing appeal compared to the competition, such as Supabase. All those other databases are well-advertised by communities. I know there is a free tier with Azure Cosmos DB. It is just not well advertised."
"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."
"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."
"The pricing model of Microsoft Azure Cosmos DB is a bit complex."
"The RU's use case determines our license fees."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
18%
Manufacturing Company
10%
Insurance Company
5%
Computer Software Company
14%
Comms Service Provider
12%
Financial Services Firm
11%
Manufacturing Company
6%
 

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?
The solution was a new product, so we didn't have a cost of ownership before. The cost has not surprised us. It's not been an issue. If we were doing multi-master replication globally, the cost wou...
What needs improvement with Microsoft Azure Cosmos DB?
Using it is easy. We are having trouble optimizing it. I'm not a technical person, so I couldn't explain why, but we're not getting the performance we were expecting. I'm sure it's probably an us p...
 

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: December 2024.
824,053 professionals have used our research since 2012.