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

Microsoft Azure Cosmos DB vs Neo4j Graph Database 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

Microsoft Azure Cosmos DB
Ranking in NoSQL Databases
3rd
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
81
Ranking in other categories
Database as a Service (DBaaS) (6th), Managed NoSQL Databases (1st), Vector Databases (3rd)
Neo4j Graph Database
Ranking in NoSQL Databases
9th
Average Rating
8.6
Reviews Sentiment
7.7
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2025, in the NoSQL Databases category, the mindshare of Microsoft Azure Cosmos DB is 2.4%. The mindshare of Neo4j Graph Database is 4.2%, up from 3.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases
 

Featured Reviews

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.
RT
Delivers superior search and data aggregation capabilities
Neo4j helps with advanced search needs, providing good search results and aggregates compared to MongoDB. Aggregating with MongoDB can be difficult; however, with Neo4j, it's easier. Aggregating data, backing up, and creating new clusters are user-friendly from the back end. In DevOps web deployment, we noticed no database issues. We created Docker instances and set them up efficiently, managing databases up to 50 gigabytes.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Azure Cosmos DB offers numerous data connectors that provide a platform for seamless integration with various platforms and visualization tools such as Power BI. It allows connection via multiple data connectors to integrate data in any desired format."
"Microsoft Azure Cosmos DB offers exceptional stability, boasting a reliability rating of 99.95 percent."
"Microsoft Azure Cosmos DB is easy to use and implement for application programmers."
"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."
"I would rate Microsoft Azure Cosmos DB a ten out of ten."
"Since it's a managed service, Azure backend handles scalability. From a user's perspective, we don't need to worry about scalability."
"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."
"Azure Cosmos DB's graph queries are its most valuable feature. Although I have not yet explored vector search, it's coming to Cosmos DB, and I plan to look into it. Having data in a flat file format in a document database speeds up processes, which is the primary purpose. Additionally, Cosmos DB's use of the Mongo platform makes it intuitive and cost-effective."
"Creates the ability to visualize outputs."
"The solution's best feature is how it differs from traditional SQL databases. It's hard to map people and find those near me in SQL, which requires long, complex queries. Neo4j Graph Database makes this easier with simpler queries. It also supports more data types, like JSON, which SQL doesn't."
"It is good for search-based tasks, providing solid search results and aggregate results."
"For now, the tool doesn't break down or stop, so it is quite stable."
"Enables people to understand what the business problem is and how the technology helps."
"As a graph database, I am surprised at their performance and response time."
 

Cons

"The query is a little complex. SQL server should have more options. But the query should be better."
"I hope they improve the service. Before last year, improvements on Cosmos DB were very slow."
"I would like the speed of transferring data to be improved."
"The one thing that I have been working on with Microsoft with regard to this is the ability to easily split partitions and have it do high-performance cross-partition queries. That is the only place where either our data size or our throughput has grown beyond one partition, so being able to do cross-partition queries efficiently would be my number one request."
"A limitation in Azure Cosmos DB is the 2 MB document size. Developers need more systemic support in chaining multiple documents if more than 2 MB is required."
"Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand."
"Microsoft Azure Cosmos DB's performance could be better. In large volumes of documents, the querying process becomes slow and complicated."
"I don't think Cosmos DB has improved our organization. People are using it, but I'm not sure it's the best solution. For one, it's costly. Also, there are other issues with it. You cannot get all the records simultaneously. You can only get it in chunks of 1,500 maximum."
"For me, when the tool was deployed on an on-premises model, it was a little bit difficult the first time."
"So far, we have not had any issues and are happy with the product in general."
"The only problem is that the community is quite small."
"The tool could improve by having more resources, especially for Golang, which we use. It lacks good basic libraries and doesn't have an ORM (Object-Relational Mapping) tool, which many NoSQL databases have. We thought about building an ORM for the Neo4j Graph Database but are too busy."
"There are concerns about performance and whether the tool can necessarily scale to provide the solution."
 

Pricing and Cost Advice

"Everything could always be cheaper. I like that Cosmos DB allows us to auto-scale instead of pre-provisioning a certain capacity. It automatically scales to the demand, so we only pay for what we consume."
"Cost isn’t a big hurdle for us right now. The solution is not costly."
"The solution is very expensive."
"The RU's use case determines our license fees."
"Its pricing structure is quite flexible."
"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."
"Pricing is mid- to high-end."
"Cosmos DB is a highly cost-optimized solution when used correctly."
"The tool is not expensive."
"The solution is open source so that you can use it for free. They also offer an enterprise version with its billing. If your company is earning well, I suggest using the enterprise version. Otherwise, you can deploy it on your own cloud and pay based on usage."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
841,605 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
12%
Legal Firm
12%
Comms Service Provider
11%
Financial Services Firm
9%
Financial Services Firm
16%
Computer Software Company
14%
Energy/Utilities Company
11%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

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?
Overall, it is a good resource. I am not aware of the background, but it seems to currently support only JSON documents. They could expand their scope to support other types of data, such as XML or...
What is your experience regarding pricing and costs for Neo4j?
The solution is open source so that you can use it for free. They also offer an enterprise version with its billing. If your company is earning well, I suggest using the enterprise version. Otherwi...
What needs improvement with Neo4j Graph Database?
The only problem is that the community is quite small.
What is your primary use case for Neo4j Graph Database?
We have used Neo4j in microservices. In one of the microservices, we used Neo4j since we have some requirements similar to MongoDB plus Elasticsearch. It performs both functions. Instead of doing t...
 

Also Known As

Microsoft Azure DocumentDB, MS Azure Cosmos DB
No data available
 

Overview

 

Sample Customers

TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Walmart, Telenor, Wazoku, Adidas, Cerved, GameSys, eBay, Schleich, ICIJ, die Bayerisch, Megree, InfoJobs, LinkedIn
Find out what your peers are saying about Microsoft Azure Cosmos DB vs. Neo4j Graph Database and other solutions. Updated: March 2025.
841,605 professionals have used our research since 2012.