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

Amazon Neptune vs MongoDB Enterprise Advanced comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 8, 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
MongoDB Enterprise Advanced
Ranking in Managed NoSQL Databases
4th
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
82
Ranking in other categories
Open Source Databases (5th), NoSQL 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 MongoDB Enterprise Advanced is 10.7%, up from 6.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Mindshare Distribution
ProductMindshare (%)
MongoDB Enterprise Advanced10.7%
Amazon Neptune6.4%
Other82.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.
FG
Architecte Cloud at Visiativ SA
Offers reliable engine for legacy needs but requires enhanced cost management and AI features
While MongoDB is a good product, it is also an expensive product for support, and its scalability is acceptable, but the big problem with MongoDB is the cost. For security in MongoDB, we work with encrypted databases by default, but we have not contracted the security options in our contract because it is too expensive, so we only implement encrypted databases without the security pack, which is very expensive for us; in security, we are at the first steps, just using encrypted databases. I think additional features needed in MongoDB include perhaps vector databases, as I think they are not supported right now.

Quotes from Members

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

Pros

"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."
"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 initial setup is actually simple."
"The community is great if you have problem."
"The solution is user-friendly with a good object retrieval feature."
"I think that MongoDB isn't too structured, and that's good for our technical team because they are able to search through the database better than if they are using SQL Server."
"It facilitates the generation of heatmaps for graphical data analysis."
"It is very easy to create a MongoDB cluster. You can deploy three nodes in one hour. You can do small configurations to enable routing. It is easy to implement."
"The solution is stable and the performance is good."
"The support from MongoDB has been great; we had to work with them during the data validation and support was helpful, with a lot of people giving revisions during the migration and working for every dollar paid, and we had a good experience with their technical support team."
"The solution's most important aspect is its seamless database."
 

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."
"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."
"In my scenario, the integration wasn't easy because ................in Java."
"When I want to connect to a node, I need to supply the certificate that MongoDB trusts, even though I use an admin password."
"MongoDB should improve its data loading part."
"The user interface is not as friendly as Oracle, which is something that can be improved."
"There should be better integration with other databases."
"The MongoDB documentation can be a little complicated sometimes."
"So I would say our compatibility and performance are the two things that came up that I know in the project we had problems with."
"The improvements could be made to intelligence to detect disk storage and prevent MongoDB from crashing."
"It is important to note that MongoDB has limitations since it can only be used for specific use cases. For example, for master data, I would want to pick keys using an RDBMS, but for attachments, I would choose MongoDB."
 

Pricing and Cost Advice

"Microsoft Azure and Amazon AWS are on par for pricing and Google has been raising its prices."
"There is an enterprise license and it could be cheaper. We are using the free open source version."
"At the moment, all customers are using the community version."
"I believe that the licensing fees are paid on a yearly basis."
"MongoDB is an open-source product."
"MongoDB is an open-source solution."
"It is rather expensive."
"I currently use the solution's community edition which is free."
"There are different licenses available to be purchased, such as individual, premium, or enterprise."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
893,244 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
15%
Manufacturing Company
8%
Computer Software Company
7%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business36
Midsize Enterprise13
Large Enterprise39
 

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 MongoDB?
MongoDB's approach to handling data in documents rather than traditional tables has been particularly beneficial.
What is your experience regarding pricing and costs for MongoDB?
I think it depends on the provider. For example, on DigitalOcean, they have strict routing. You have to whitelist an IP address, or you risk getting DDoS. Then if you're going for the Atlas one tha...
What needs improvement with MongoDB?
I don't really have a deep dive into it, but I see that MongoDB Enterprise Advanced has RAG and Vertex support. However, we really didn't use it because I think one thing also is that Prisma, the O...
 

Overview

 

Sample Customers

Intuit, Pearson, Samsung, Ignition One, Lifeomic, Blackfynn, Paysense
Facebook, MetLife, City of Chicago, Expedia, eBay, Google
Find out what your peers are saying about Amazon Neptune vs. MongoDB Enterprise Advanced and other solutions. Updated: April 2026.
893,244 professionals have used our research since 2012.