Likelihood to Recommend
DynamoDB is a great service if you are looking for a quick and easy way to store NoSQL data in the cloud and do not want to be concerned with managing the server or infrastructure. If you are already invested in AWS, the value proposition is even higher as it works very well with the other services that AWS provides.
Read full review
Neo4J is great for creating network graphs or illustrating how things are related. It is also good for finding individuals or things that have greater influence than others in a system. It is not appropriate if you have standard data sets that can be analyzed using conventional methods or visualized using
, for example.
Read full review Pros It's very easy to get started, creating a table with a partition/sort key and you're on your way. You can scale up and down your read/write IO as needed. You can store structured and unstructured data. It works great with Web Development as it's JSON based. Read full review Mature Query language, I found Cypher QL to be mature in handling all sorts of problems we throw at it. Its expressive enough to be intuitive while providing rich features for various scenarios. Native support for REST API, that makes interacting with Neo4J intuitive and easy. Support for Procedures in Java, procedures are custom code that could be added to the Neo4J to write custom querying of data. The best part about the procedures is it could be invoked using the REST API. This allows us to overcome any shortcomings from their Cypher query language. Nice UI and interface for executing the Query and visualizing the response. UI access controlled by User credentials allows for neat access controls. Awesome free community edition for small-scale projects. Read full review Cons Complex searching (no support for case-insensitive or full-text search). Only supports up to two-key indexes. Requires choosing the indexes up-front when doing searches. Does not have an SQL compatible query front-end. No join-table support (requires putting all data into one table). Read full review One of the hardest challenges that Neo4j had to solve was the horizontal scaling problem. I am not updated on recent developments, but at the time of my use, I couldn't find a viable solution. Neo4j does not play with other open source APIs like Blueprint. You have to use the native Neo4j API. There wasn't a visual tool to see your data. Of course, third party tools are always available, but I would have loved something which came with the Neo4j bundle. I love that Docker comes bundled with Kitematic, so it's not wrong to hope that Neo4j could also ship with some default visualization software. Read full review Likelihood to Renew
We will most likely continue to use DynamoDB for certain use-cases. If we stopped using DynamoDB as often, it would likely be because we started using Aurora Serverless more. Aurora Serverless may offer similar availability, management and cost benefits while allowing developers to use their MySQL tools and experience.
Read full review Usability
Amazon DynamoDB has quite a lot of advantages :
Serverless to make usage and administration a breeze on a daily basis
Very fast lookup in a list of millions of items
Replication across region is quite easy to setup, albeit at an increased cost.
But despite all this, I would not give it a perfect 10 because I find its item size limit way too small for some of my uses.
Read full review
[Based on] Query Language, Performance on small and large data sets, integration and deployment, analysis, API support, Interactive UI.
Read full review Support Rating
I have never contacted support for Amazon DynamoDB.
And I'm adding quite a lot of useless words to this explanation in order to reach the word count that is required despite the heading saying that I can skip this question. It seems there is then a bug here but what software does not have bugs?
Read full review Alternatives Considered
We evaluated using MongoDB or Amazon DyanmoDB. For us, the biggest advantage is that there's no maintenance cost for Amazon DynamoDB. Mongo gets complicated when you setup sharding. With Amazon DynamoDB, it's literally a push of button to increase throughput. This saves time and money on DevOps resources.
Read full review
Neo4j is a graph store and has different use cases compared to another NoSQL Document store like
is a bad choice when joins are common as existing operators for joining two documents (similar to tables in a relational store) as Mongo 3.5 use SQL like join algorithms which are expensive.
is a great choice when distributed schemaless rich document structures are important requirements. Cross document transaction support is not native to
yet, whereas Neo4J is ACID complaint with all its operations.
Read full review Return on Investment Since the Amazon manages the instance, the amount of time a developer needs to spend configuring the database is less. For comparison, if we were to manage the same instance manually, we need to set up EC2 instance, install the DB, setup backup scripts, track backup failures, which is a great overhead for the dev. Using DynamoDB this overhead is reduced and hence having a great ROI. Great documentation and easy setup makes an easy learning curve to transition to DynamoDB. Only caveat is as with any database, the data structure should be thoroughly analyzed for types of querying because there are limitations with the DynamoDB API. Ties very well with rest of the Amazon eco system. Having rest of the applications in Amazon allows managing the application security a breeze. Read full review Positive: Less complex queries on graph structures, than in relational databases. Negative: maintenance is a huge deal, things doesn't work and break, requiring lengthy restore operations. Read full review ScreenShots Amazon DynamoDB Screenshots