Amazon DynamoDB vs Neo4j AuraDB comparison

"We don't have to administer the tool."

"Stability-wise, I rate the solution a ten out of ten. I've never faced any problems."

"It is a NoSQL product."

"Amazon DynamoDB allows you to configure your read-write capacity and create a single global table that can be accessed with any other region."

"Storing is a valuable feature. We can store as an entire object rather than the traditional structure of the data."

"The best feature is NoSQL."

"The most valuable features are the flexibility and the compatibility options without needing to use any additional services or software. It is an independent solution that doesn't need other solutions to operate."

"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."

"From my experience, I particularly like the professional version. Initially, developers often start with the free variant. Once the project grows, we switch to the professional version, which offers multiple databases, expanded memory, and better scalability. This allows us to handle more data and use cloud scaling features."

"The tool is easy to use."

"I like the idea of graphs and nodes and the possibilities Neo4j AuraDB offers."

"The most valuable features of Neo4j AuraDB include its flexible data model and broad language support."

"The most beneficial things in terms of AuraDB are its speed, its good pricing, the multi-cloud availability."

"Integrating the front-end language with Neo4j AuraDB is a very easy process."

"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 would work fast if a contact center is in the same region."

"Defining simple expressions and queries can be slightly complicated due to DynamoDB's unique JSON syntax. This can be confusing, especially for beginners."

"The process of making a query could be optimized."

"The response time for data queries should be less than a second"

"The solution has size limitations. It also needs to be more user-friendly."

"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."

"During the product's initial setup phase, there were some issues due to disconnections in the tool's network."

"I've experienced it crashing a few times, so stability could be better."

"There’s room for improvement in Neo4j AuraDB, especially on the developer side. The learning curve can be steep, and the interface for developing and pushing code can be unnecessarily complex. It might be beneficial to simplify this process to help developers ramp up more quickly. Working with graph databases like Neo4j can be more challenging than standard databases, particularly for juniors and those new to graph technology. Streamlining the development process could make it easier for new users to get up to speed. This would be particularly useful for teams with less experience in graph databases. If I could add a feature to Neo4j AuraDB, I’d focus on improving the Bloom interface. It’s excellent for visualizing smaller datasets, but navigating through it becomes challenging as the data grows—say, past 100,000nodes. The interface works well for beginners but doesn’t scale effectively for more advanced users of large datasets. I want a UI that bridges the gap between the easy-to-use Bloom interface and more complex, text-based tools. This would help manage larger datasets more efficiently and improve performance."

"In terms of AuraDB, the conversations have always been around scalability."

"Some features can help if they can visualize graphs better."

"It's an expensive solution"

"Compared to a high-end relational database, it's cheap."

"On a scale of one to ten, where one is a high price and ten is a low price, I rate the pricing a seven. It is not the cheapest, but it is not the costliest either."

"The product is expensive"

"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."

"Amazon DynamoDB is a cheap solution."

"We previously paid around $20,000 a month for MongoDB, and now we're paying just $4,000 monthly for Amazon DynamoDB."

"It is a little expensive."

"The tool's enterprise edition is very expensive."

"I used the free tier."

"Neo4j AuraDB is reasonably priced, especially considering it removes the need for cloud administration and associated costs. It's a good deal for the professional version, as it includes managed services, which reduces the overhead compared to setting up your own infrastructure. The cost can be higher for enterprise-scale projects, but that's often due to the scale and complexity of the project rather than the product itself. Startups sometimes overestimate their needs and jump to enterprise pricing too quickly, leading to higher costs than necessary."

"I am using an open-source version of Neo4j AuraDB."