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

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.2
Number of Reviews
45
Ranking in other categories
No ranking in other categories
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
 

Mindshare comparison

As of May 2026, in the Managed NoSQL Databases category, the mindshare of Amazon DynamoDB is 10.6%, down from 16.6% compared to the previous year. The mindshare of Amazon Neptune is 6.4%, down from 11.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Amazon DynamoDB10.6%
Amazon Neptune6.4%
Other83.0%
Managed NoSQL Databases
 

Featured Reviews

DG
Lead SRE at JavaTech
Has improved infrastructure availability and simplified integration through reliable cloud-based data management
Amazon DynamoDB is readily available, and we do not have to worry about downtime unless there is a global outage. From a cost perspective, it presents a challenge. The primary feature is constant availability without concerns about server maintenance or ensuring database uptime, as AWS manages everything from their end. We simply set up the database and allocate it to customers according to their requirements, making it an easy and smooth transition. Regarding security, being in the cloud provides numerous security features. Amazon DynamoDB operates at the backend within our three-tier architecture. We have front hosting, business logic or application server in the middle, and databases at the backend. Additionally, we implement security layers such as SSL, creating a highly secure environment. The solution has proven to be reliable thus far.
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.

Quotes from Members

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

Pros

"It has helped us build our product from zero point to the end."
"The most valuable features are the flexibility and the compatibility options without needing to use any additional services or software, as it is an independent solution that doesn't need other solutions to operate."
"The fact that it is so easy to create tables and provision for known throughput saved us a lot of time, especially because we are deploying multiple environments and multiple regions."
"The most valuable feature of this solution is the non-relational database."
"The best feature is NoSQL."
"DynamoDB is a key-value database, and it's valuable if you have simple scan queries and don't need to do point searches."
"Speed is the most valuable feature. The speed to store and retrieve data from it."
"Being serverless, it alleviates concerns about scalability and failover."
"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."
"Relational databases are never good at identifying patterns in graphs or other similar relationships, whereas Amazon Neptune is."
 

Cons

"Querying data on the solution is quite limited, but this is like any other NoSQL database. It's the most common criticism of the NoSQL database in general."
"I would rate the stability a seven out of ten. We faced some configuration issues."
"Support is better if using a paid version."
"About 30% of the time, Amazon's support lacked enough knowledge to solve my problems."
"As more data comes in, it becomes more expensive."
"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 solution's initial setup is a bit complex if you want it for something more specific."
"The only challenge I face with Amazon DynamoDB is that with the partition key and secondary key, the query doesn't become very easy."
"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."
"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."
"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."
 

Pricing and Cost Advice

"Given the services and benefits provided by AWS, the solution's pricing is average."
"For our use case usage, DynamoDB's pricing was okay. However, for high-traffic applications, the pricing structure becomes less attractive."
"It is costly. To reduce the costs, users need to read the node in front of it. For read-heavy groups, cache optimization can help manage costs.I can't disclose specific pricing, but it's competitive compared to others in the market, and this information is easily accessible online"
"The solution is cheaper than Cosmos DB."
"Amazon DynamoDB is cheap."
"Amazon DynamoDB is a cheap solution."
"It's an expensive solution"
"The product is expensive"
"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.
893,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
10%
Manufacturing Company
8%
Marketing Services Firm
7%
Financial Services Firm
20%
University
12%
Computer Software Company
11%
Insurance Company
7%
 

Company Size

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

Questions from the Community

What needs improvement with Amazon DynamoDB?
The only challenge I face with Amazon DynamoDB is that with the partition key and secondary key, the query doesn't become very easy. The construction of that schema is a bit tricky because once you...
What is your primary use case for Amazon DynamoDB?
Our main use case for Amazon DynamoDB is storing quick metadata information about any of the image artifacts that we collect from our customers. We generally store this in Amazon DynamoDB in multip...
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: April 2026.
893,164 professionals have used our research since 2012.