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

Amazon Neptune 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 Neptune
Ranking in Managed NoSQL Databases
8th
Average Rating
8.6
Reviews Sentiment
4.5
Number of Reviews
4
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 January 2026, in the Managed NoSQL Databases category, the mindshare of Amazon Neptune is 7.2%, down from 15.4% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 16.4%, down from 17.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Market Share Distribution
ProductMarket Share (%)
Microsoft Azure Cosmos DB16.4%
Amazon Neptune7.2%
Other76.4%
Managed NoSQL Databases
 

Featured Reviews

Reviewer3028812 - PeerSpot reviewer
Back End Developer at Zeta
Multiple graph models and languages support lead to efficient use, yet community growth brings challenges
The onboarding part and documentation where we could ideally use Amazon Neptune is excellent. Amazon Neptune as a product by AWS is exceptional because it supports multiple graph models such as RDF and property graph. It also has support for multiple querying languages such as Gremlin, SparkQL, and OpenCypher. It is very comprehensive in supporting every requirement we had at Zetta. Amazon Neptune's best features include its multiple servers, each supporting different languages such as OpenCypher, SparkQL, and RDF. For the same RDF graph or property graph, we could use multiple languages to query on different servers. This is exceptional because we have one graph DB with two endpoints exposed where we could interact with different languages on the same graph. Additionally, Amazon has a Sagemaker Jupyter Notebook which interacts with the Amazon Neptune database itself, providing a clean UI for representing nodes since the Jupyter Notebook has predefined graph representation capabilities through queries.
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

"The initial setup is actually simple."
"Relational databases are never good at identifying patterns in graphs or other similar relationships, whereas Amazon Neptune is."
"Amazon Neptune as a product by AWS is exceptional because it supports multiple graph models such as RDF and property graph, and it also has support for multiple querying languages such as Gremlin, SparkQL, and OpenCypher, making it very comprehensive in supporting every requirement we had at Zetta."
"Amazon Neptune as a product by AWS is exceptional because it supports multiple graph models such as RDF and property graph, and it also has support for multiple querying languages such as Gremlin, SparkQL, and OpenCypher, making it very comprehensive in supporting every requirement we had at Zetta."
"Microsoft Azure Cosmos DB simplifies the process of saving and retrieving data."
"Latency and availability are incredible."
"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."
"It works reasonably fast. You can retain the original format of the document as received by the third-party system."
"For example, we have people spread across multiple locations; if they update data in Australia, we can access it in another location within a fraction of a second."
"The benefits of Microsoft Azure Cosmos DB were immediate for us."
"Cosmos is preferred because of its speed, robustness, and utilization. We have all the merchandising information in Cosmos DB, which provides concrete and optimized data when searching for new products on the site. It is faster than other relational databases."
"I definitely recommend Microsoft Azure Cosmos DB."
 

Cons

"We had a strict time constraint, and it took many sleepless nights to find information in the documentation."
"Amazon Neptune could improve by spreading more awareness for others to have an understanding of the solution because the technology is fairly new. The developer community and larger community do not understand it yet."
"We had a strict time constraint, and it took many sleepless nights to find information in the documentation."
"In my scenario, the integration wasn't easy because ................in Java."
"We had to go to forums to check if it was failing for everyone else. It was surprising that a large organization like Microsoft doesn't provide an official statement about the maintenance or issues that could impact our overall usage."
"We should have more freedom to tweak it and make our own queries for non-traditional use-cases."
"One of the most frustrating aspects of Microsoft Azure Cosmos DB right now is that you can only store one vector per document."
"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."
"There is room for improvement in their customer support services."
"The customer service is lacking. We have a premier support agreement, but support is hit and miss."
"Azure Cosmos DB could be better for business intelligence and analytical queries."
"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."
 

Pricing and Cost Advice

"Microsoft Azure and Amazon AWS are on par for pricing and Google has been raising its prices."
"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 gave us three accounts for $400. We pay according to the usage."
"Its pricing structure is quite flexible."
"Because of the lack of understanding about RUs, the costs become unpredictable. It sometimes goes over the budget."
"Cosmos DB's pricing structure has significantly improved in recent months, both in terms of its pricing model and how charges are calculated."
"The tool is not expensive."
"Its pricing is not bad. It is good."
"Pricing is mid- to high-end."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
12%
University
12%
Insurance Company
7%
Legal Firm
13%
Financial Services 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 Enterprise21
Large Enterprise58
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon Neptune?
The cost aspects were managed by our SRE team who provisioned the instances. The pricing structure is similar to how EC2 instance pricing varies. I was informed that it was somewhat expensive, thou...
What needs improvement with Amazon Neptune?
The main issue was the limited community of Amazon Neptune users, which meant everything needed to be explored independently. Although this was adventurous, it required more time investment in the ...
What is your primary use case for Amazon Neptune?
We managed traffic at Zetta, and traffic would be moving between multiple services in our microservice architecture. Because of this setup, we were using Amazon Neptune to understand how many reque...
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?
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...
 

Also Known As

No data available
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Overview

 

Sample Customers

Intuit, Pearson, Samsung, Ignition One, Lifeomic, Blackfynn, Paysense
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about Amazon Neptune vs. Microsoft Azure Cosmos DB and other solutions. Updated: December 2025.
881,082 professionals have used our research since 2012.