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

Amazon DynamoDB vs Amazon Neptune comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 3, 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 DynamoDB
Ranking in Managed NoSQL Databases
2nd
Average Rating
8.2
Reviews Sentiment
6.4
Number of Reviews
43
Ranking in other categories
No ranking in other categories
Amazon Neptune
Ranking in Managed NoSQL Databases
7th
Average Rating
8.6
Reviews Sentiment
4.5
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the Managed NoSQL Databases category, the mindshare of Amazon DynamoDB is 13.1%, down from 21.8% compared to the previous year. The mindshare of Amazon Neptune is 7.7%, down from 14.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Market Share Distribution
ProductMarket Share (%)
Amazon DynamoDB13.1%
Amazon Neptune7.7%
Other79.2%
Managed NoSQL Databases
 

Featured Reviews

MohamedBouzidi - PeerSpot reviewer
Streamlined data management with robust automation and easy replication
Amazon DynamoDB has been a reliable service that is very performant and meets our expectations. Its automation capacity reduces the need for more personnel, which aligns perfectly with our strategy of focusing on serverless services. The ease of data replication between regions is a significant benefit since it was already integrated into the solution.
Reviewer3028812 - PeerSpot reviewer
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.

Quotes from Members

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

Pros

"The best feature is NoSQL."
"The most valuable feature of the solution is its performance."
"Capable of auto-scaling and integrates easily with other tools"
"Amazon DynamoDB is serverless and fast, and we can use different keys along with it in our code."
"The latency feature is precious."
"We don't have to administer the tool."
"We use the single table design pattern extensively since it helps us describe very complex patterns and data types on the table."
"Amazon DynamoDB allows you to configure your read-write capacity and create a single global table that can be accessed with any other region."
"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 initial setup is actually simple."
 

Cons

"The design patterns and the documentation for this solution could be improved. In a future release, we would like to see an improvement of the data push options as we sometimes experience blockers when moving data."
"The solution's efficiency and performance should be faster than other databases."
"Currently, there is no option for a scheduled refresh in this solution. We want the data to be populated into DynamoDB on a timely basis. Currently, you have to go to the DynamoDB table and hit the refresh button to populate it with the new data. If you have connected DynamoDB to a BI application for creating visualizations with charts, graphs, or other things, you would want it to get updated as per the schedule so that you have updated visualizations in your BI application."
"The primary key is quite slow."
"If you purchase the support plan, their support team is good. If not, it takes two to three days to respond, sometimes even more."
"In future releases, I would like a feature that lets us store information about public holidays or weekends. When customers call during those closed periods, we could use DynamoDB to trigger an automatic message. So this would eliminate the need for agents to manually inform customers."
"I'd like to see better integration with Cognito. It has the integration, but I'd like to see a little more ease of setup. If you have multiple customers and you want the database to enforce who can see what, you can treat DynamoDB so that each row has permissions. You can set this up, but it's a little more of a science project to make Cognito and DynamoDB work well to do protection of individual rows. So I'd like that to be more wizard or easy to set up."
"The documentation is not good enough."
"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."
"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."
 

Pricing and Cost Advice

"It's an expensive solution"
"We previously paid around $20,000 a month for MongoDB, and now we're paying just $4,000 monthly for Amazon DynamoDB."
"The pricing is based on Lambda function usage. So, if a Lambda function is invoked with every call, and we receive 5,000 calls daily, that means 5,000 Lambda invocations."
"Given the services and benefits provided by AWS, the solution's pricing is average."
"The product is expensive"
"The solution's pricing is good, and it's not expensive."
"Amazon DynamoDB is a cheap solution."
"Compared to a high-end relational database, it's cheap."
"Microsoft Azure and Amazon AWS are on par for pricing and Google has been raising its prices."
report
Use our free recommendation engine to learn which Managed NoSQL Databases solutions are best for your needs.
868,759 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Financial Services Firm
16%
Manufacturing Company
8%
Comms Service Provider
7%
Financial Services Firm
20%
Computer Software Company
17%
Construction Company
7%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise2
Large Enterprise17
No data available
 

Questions from the Community

What needs improvement with Amazon DynamoDB?
The user interface could be improved to make it more intuitive. From a design and solution perspective, it's really good, but the interface always has room for enhancement.
What is your primary use case for Amazon DynamoDB?
We use Amazon DynamoDB for data lookups with the consultancy.
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...
 

Overview

 

Sample Customers

Samsung, Snapchat, Capital One, Expedia, Tinder, Airbnb, Comcast, Lyft, Redfin, Netflix, Adobe
Intuit, Pearson, Samsung, Ignition One, Lifeomic, Blackfynn, Paysense
Find out what your peers are saying about Amazon DynamoDB vs. Amazon Neptune and other solutions. Updated: September 2025.
868,759 professionals have used our research since 2012.