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
 

Categories and Ranking

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

Featured Reviews

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.
AR
Easy to use and not so expensive
For first-time users, if you don't know much about the tool, I think you should go with a document-based DBMS tool. I had to use the tool because I learned about it in college. My advice to others is that they need to learn about the tool, nodes, and vertices and then purchase Neo4j Graph Database. It will be a little bit difficult for new users to know what is the meaning of a node, what vertices are, how to use it, or how an application can use it. The tool is easy for new users as it is an intuitive tool. I rate the tool a nine out of ten.

Quotes from Members

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

Pros

"It is a NoSQL database."
"Microsoft Azure Cosmos DB is fast, and its performance is good compared to normal SQL DB."
"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."
"It works reasonably fast. You can retain the original format of the document as received by the third-party system."
"The speed is impressive, and integrating our power-up database with Kafka was an improvement."
"Cosmos DB's greatest strengths are its easy setup and affordability, especially for those who understand its usage."
"Microsoft Azure Cosmos DB has helped to improve efficiency, providing good response times and allowing the storage of AI process results, which is crucial for feedback loops."
"It is easy to use because you don't need to know much about Cosmos DB or have prior experience."
"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."
"Creates the ability to visualize outputs."
"For now, the tool doesn't break down or stop, so it is quite stable."
"As a graph database, I am surprised at their performance and response time."
"Enables people to understand what the business problem is and how the technology helps."
 

Cons

"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."
"Slight enhancements in integration interfaces, expanded dashboard functionalities, and broader use-case support would be beneficial."
"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."
"In the long run, there should be an addition of more features, especially because this space is evolving quickly. It all boils down to how many more features you are adding, how many integrations you are supporting, and how many more APIs you have that are standard APIs."
"We expect Cosmos DB to lead on that. There is potential for improved security features, which is important for data storage, especially for Dell Technologies."
"It should offer a simple user interface for querying Microsoft Azure Cosmos DB."
"One area of improvement for Cosmos database is the auto-scaling of RUs during high loads. It would be beneficial if the database could automatically scale resources rather than requiring manual adjustments."
"I have to say technical support is not very good as it takes too long. Sometimes it can take them two or three days to respond to your ticket."
"There are concerns about performance and whether the tool can necessarily scale to provide the solution."
"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 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."
 

Pricing and Cost Advice

"The solution is very expensive."
"When we've budgeted for our resources, it's one of the more expensive ones, but it's still not very expensive per month."
"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."
"Pricing, at times, is not super clear because they use the request unit (RU) model. To manage not just Azure Cosmos DB but what you are receiving for the dollars paid is not easy. It is very abstract. They could do a better job of connecting Azure Cosmos DB with the value or some variation of that."
"The pricing model of Microsoft Azure Cosmos DB is a bit complex."
"The customer had a high budget, but it turned out to be a little bit cheaper than what they expected. I am not sure how much they have spent so far, but they are satisfied with the pricing."
"The pricing for Microsoft Azure Cosmos DB is good. Initially, it seemed like an expensive way to manage a NoSQL data store, but so many improvements that have been made to the platform have made it cost-effective."
"The RU's use case determines our license fees."
"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."
"The tool is not expensive."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
829,541 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Comms Service Provider
12%
Financial Services Firm
11%
Manufacturing Company
6%
Computer Software Company
18%
Financial Services Firm
15%
Energy/Utilities Company
10%
Manufacturing Company
8%
 

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's pricing is competitive, though there is a need for more personalized pricing models to accommodate small applications without incurring high charges. A suggestion is to implement ...
What needs improvement with Microsoft Azure Cosmos DB?
For streaming platforms, Azure Cosmos DB could improve efficiency in data storage. Indexing can also be better. Enhanced capabilities are necessary to manage increased data amounts more effectively...
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 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 databa...
What is your primary use case for Neo4j Graph Database?
We're building a social media platform, which is a great use case for the product. It helps connect people. For example, if we're friends on Facebook, I can get suggestions for people near me or re...
 

Also Known As

Microsoft Azure DocumentDB, MS Azure Cosmos DB
No data available
 

Learn More

 

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