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.0
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 June 2026, in the Managed NoSQL Databases category, the mindshare of Amazon DynamoDB is 10.4%, down from 16.3% compared to the previous year. The mindshare of Amazon Neptune is 6.1%, down from 10.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Amazon DynamoDB10.4%
Amazon Neptune6.1%
Other83.5%
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

"The ability to store multiple data attributes is crucial. For example, in a contact flow, if a customer calls, we can integrate DynamoDB dynamically. We need only the customer's mobile number as the primary key, which is stored in the DynamoDB table."
"Never used the support. I got all the information from the documentation."
"The platform is easy to develop and configure."
"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."
"There aren't any issues with the product; on the contrary, it has helped us build our product from zero point to the end, and I like that there's no need for external configurations or DevOps engineers."
"We switched to DynamoDB from a relational database that would've had scale problems and would've cost a lot of money to run at scale. DynamoDB allows us to match expense to usage. When not many people are using and it's a quiet day, there is a low cost. On a busy day, there is a higher cost. We get good performance along the way and less maintenance on the database."
"The technical support team is always available to help us."
"The application runs much faster and the query response time is three to five times faster when compared to Google Datastore."
"Relational databases are never good at identifying patterns in graphs or other similar relationships, whereas Amazon Neptune is."
"The initial setup is actually simple."
"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."
 

Cons

"I initially faced issues with the solution's stability, performance, and security."
"If you purchase the support plan, their support team is good. If not, it takes two to three days to respond, sometimes even more."
"There are some issues, like if we missed something or somehow were not able to store the data, then it was quite difficult for us to get back that data."
"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."
"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."
"Defining simple expressions and queries can be slightly complicated due to DynamoDB's unique JSON syntax. This can be confusing, especially for beginners."
"Some things must be implemented manually and that takes a lot of time."
"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."
"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."
 

Pricing and Cost Advice

"The solution's pricing is good, and it's not expensive."
"Amazon DynamoDB is cheap."
"Given the services and benefits provided by AWS, the solution's pricing is average."
"Its subscription cost is lower than similar databases offered by other vendors."
"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"
"Amazon DynamoDB is a cheap solution."
"Compared to a high-end relational database, it's cheap."
"It's an expensive solution"
"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.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Construction Company
11%
Computer Software Company
10%
Manufacturing Company
8%
Financial Services Firm
19%
University
12%
Computer Software Company
10%
Construction Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business24
Midsize Enterprise1
Large Enterprise19
No data available
 

Questions from the Community

What needs improvement with Amazon DynamoDB?
In terms of improvement for Amazon DynamoDB, I can see that it supports a very good amount of querying, but if they can enhance that part by providing aggregation functions similar to SQL and other...
What is your primary use case for Amazon DynamoDB?
Amazon DynamoDB is primarily used for data storage since it is a non-structured database.A specific example of how I use Amazon DynamoDB for data storage in my work is that we use it in correlation...
What advice do you have for others considering Amazon DynamoDB?
My advice for others looking into using Amazon DynamoDB would be that it depends on the architecture needs and budget; if they aim for cost-efficiency, they should use Amazon DynamoDB, but if they ...
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: June 2026.
900,747 professionals have used our research since 2012.