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 5, 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 Neptune
Ranking in Managed NoSQL Databases
4th
Average Rating
8.6
Reviews Sentiment
7.1
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
84
Ranking in other categories
Database as a Service (DBaaS) (6th), NoSQL Databases (3rd), Vector Databases (3rd)
 

Mindshare comparison

As of April 2025, in the Managed NoSQL Databases category, the mindshare of Amazon Neptune is 12.9%, down from 13.7% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 15.5%, down from 18.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases
 

Featured Reviews

Matthew Spieth - PeerSpot reviewer
Useful pattern identification, price well, and straightforward implementation
Relational databases are never good at identifying patterns in graphs or other similar relationships, whereas Amazon Neptune is. Amazon Neptune is good for identifying fraud and many banks are using it. For example, know that I go to certain places all the time that are connected with nodes and edges, such as gas stations, shops, and Amazon. Since people are creatures of habit, the banks can use those nodes and edges to make a model of where I like to shop and spend money. If they see something pop up that's out of character for me, then they know immediately that it is possible fraud. They can determine this because a purchase I made was somewhere I never go or because of geography.
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

"The initial setup is actually simple."
"Relational databases are never good at identifying patterns in graphs or other similar relationships, whereas Amazon Neptune is."
"We value the replication and regional availability features that Cosmos DB provides. The replication includes read replicas and write replicas. The recent addition of vectorization and similarity comparisons add values for AI workloads. The performance and scaling capabilities of Cosmos DB are excellent, allowing it to handle large workloads compared to other services such as Azure AI Search."
"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."
"We primarily use Cosmos DB because it's a managed platform service, eliminating concerns about hosting and reliability."
"The most valuable features of Microsoft Azure Cosmos DB include the TTL, the ability to scale up and down as needed, and geo-replication, which comes out of the box."
"Microsoft Azure Cosmos DB is fast, and its performance is good compared to normal SQL DB."
"The speed is impressive, and integrating our power-up database with Kafka was an improvement."
"The high speed of Azure Cosmos DB compared to other competitors is remarkable."
"Cosmos DB is effective at handling large queries."
 

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."
"In my scenario, the integration wasn't easy because ................in Java."
"The integration with other solutions needs to improve because Cosmos DB's interoperability is lacking in some scenarios. For example, I'm currently implementing Fabric. That involves migrating from environments without apps, processing data and users, and taking them to Fabric."
"There are multiple approaches to implementing multitenant architecture on Azure Cosmos DB, but there is still no single or best-recommended approach when you have a big variance in the size of your tenants. That is something that still needs to be worked on."
"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."
"Currently, it doesn't support cross-container joins, forcing developers to retrieve data from each container separately and combine it using methods like LINQ queries."
"One of our biggest pain points is the backup and restore functionality needs improvement."
"Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand."
"We encountered an issue with Cosmos DB's recently introduced hierarchical partition feature."
"The integration of the on-premise solution with the cloud can be difficult sometimes."
 

Pricing and Cost Advice

"Microsoft Azure and Amazon AWS are on par for pricing and Google has been raising its prices."
"The solution is a bit on the expensive side."
"Azure Cosmos DB is generally a costly resource compared to other Azure resources. It comes with a high cost. We have reserved one thousand RUs. Free usage is also limited."
"Right now, I have opted for the student subscription plan, for which Microsoft charges me around 100 USD. The pricing of the solution depends on the solution's usage."
"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."
"Cosmos DB gave us three accounts for $400. We pay according to the usage."
"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."
"Cosmos DB's pricing structure has significantly improved in recent months, both in terms of its pricing model and how charges are calculated."
"Most customers like the flexibility of the pricing model, and it has not been an issue. They can start small, and the cost grows with adoption, allowing efficient management of the budget. Its pricing model has not been a concern at all for any of our customers. They understand it. It is simple enough to understand. Oftentimes, it is hard to forecast the RUs, but, in general, it has been fine."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
844,944 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
20%
Financial Services Firm
17%
Government
7%
Manufacturing Company
6%
Legal Firm
12%
Computer Software Company
12%
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 is your experience regarding pricing and costs for Amazon Neptune?
When taken as part of the whole AWS contract, it was cheaper, but as a single service, Neptune was more expensive compared to Neo4j.
What needs improvement with Amazon Neptune?
Some improvements could be made by introducing a UI that would clearly show the vertices and connections, which would make it easier to visualize and debug. Additionally, the need for downtime duri...
What is your primary use case for Amazon Neptune?
So, I'm not using it currently, but when I was working with my last organization, which was a gaming company, we used Amazon Neptune for real-time fraud detection. We maintained user data, mobile d...
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?
Azure Cosmos DB is generally a costly resource compared to other Azure resources. It comes with a high cost. We have reserved one thousand RUs. Free usage is also limited.
What needs improvement with Microsoft Azure Cosmos DB?
I think Cosmos DB enhanced the benefits of NoSQL databases, offering query flexibility, partition management, and backup and restore options. These aspects are crucial, and perhaps improving the co...
 

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: March 2025.
844,944 professionals have used our research since 2012.