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

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 May 2026, in the Managed NoSQL Databases category, the mindshare of Amazon Neptune is 6.4%, down from 11.4% 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 Neptune6.4%
Other77.9%
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."
"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."
"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."
"The stability of Amazon Neptune is very good."
"I truly recommend Cosmos DB because it is a serverless product."
"The most valuable feature of Microsoft Azure Cosmos DB is its real-time analytics capabilities, which allow for turnaround times in milliseconds. This is crucial for applications like fraud detection."
"Overall, I think Microsoft Azure Cosmos DB works fine; I don't remember any case where our developers or our clients have been disappointed with it."
"When all resources are at the same point, there is no lag and in production we have experienced minimal issues, with the project live for two years without any database problems."
"Microsoft Azure Cosmos DB simplifies the process of saving and retrieving data."
"Cosmos DB performs exceptionally well and has not caused any issues that necessitate adjustments in nodes for improved performance."
"The solution is easy to use, and it is also easy to integrate with several things for database use cases."
"Our customer is very satisfied with it."
 

Cons

"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."
"Amazon Neptune could improve by spreading more awareness for others to have an understanding of the solution because the technology is fairly new."
"In my scenario, the integration wasn't easy because ................in Java."
"We had a strict time constraint, and it took many sleepless nights to find information in the documentation."
"We had a strict time constraint, and it took many sleepless nights to find information in the documentation."
"There is room for improvement in terms of stability."
"I had a challenging experience implementing the emulator with a Mac. I had to install the emulator in a Docker container because it is not natively compatible. A significant amount of time was spent researching how to enable HTTPS communication when connecting the container and the emulator."
"The query searching functionality has some complexities and could be more user-friendly."
"The customer service is lacking. We have a premier support agreement, but support is hit and miss."
"There is room for improvement in Microsoft's maintenance aspect. For example, we had a major incident at the end of December where the entire South Central region was down for our application, causing many problems due to a lack of access to the database."
"Areas of improvement for Microsoft Azure Cosmos DB include indexing. While it makes data retrieval easier, it also increases costs."
"Currently, I have no suggestions for enhancement or new implementations in Microsoft Azure Cosmos DB. However, the cost can sometimes be high, especially during cross-partition queries with large data amounts."
"The query is a little complex. SQL server should have more options. But the query should be better."
 

Pricing and Cost Advice

"Microsoft Azure and Amazon AWS are on par for pricing and Google has been raising its prices."
"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."
"Cost isn’t a big hurdle for us right now. The solution is not costly."
"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."
"I would rate Cosmos DB's cost at seven out of ten, with ten being the highest."
"Its pricing structure is quite flexible."
"The Cosmos DB pricing model, initially quite complicated, became clear after consulting with Azure Advisor, allowing us to proceed with confidence."
"It is cost-effective. They offer two pricing models. One is the serverless model and the other one is the vCore model that allows provisioning the resources as necessary. For our pilot projects, we can utilize the serverless model, monitor the usage, and adjust resources as needed."
"Its pricing is not bad. It is good."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
893,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
University
12%
Computer Software Company
11%
Insurance Company
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 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 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

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: April 2026.
893,311 professionals have used our research since 2012.