Amazon DynamoDB Reviews & Insights

AWS DynamoDB allows our company to easily access a no SQL database without the hassle of maintaining it ourselves. Service discovery, networking, and IAM are all handled natively, which makes management a breeze. We access the DB from various services in the cloud and externally. The speed and reliability have exceeded expectations.

DynamoDB makes sense in situations where NoSQL is a better choice than a relational database. It's important to have your data modeled effectively and your access patterns clearly defined. If your schema is fluid but you can rely on strong primary key access, NoSQL and DynamoDB make sense. There are more complex implementations of DynamoDB (see single table design on YouTube), but IMO, they aren't worth the effort.

We use DynamoDB for our low-latency data access for internal web-apps that require quick real-time information. It’s quite flexible for micro services and while it can be used in many different use cases we only use it for internal web apps, but could be recommended for mobile apps as well.

It’s great for server less and real-time applications. It would be great for gaming and mobile apps. However, if you need relational database and have fixed budget, do not use it. While budget can be managed, you need to be careful. Also this is not a tool for storing big data, there are other wide-column database types you could use for it ins the ad

We use Amazon DynamoDB for serverless application to store data and pull it based on user requests. The app has authentication and there are permissions assigned to that roles for access.

I believe when there are too many relations to be deal with in terms of data associations, Amazon DynamoDB wont be well suited. The data were there is more of key value pairs and lower latency request it can be used.

The most beneficial aspect of Amazon DynamoDB is that it is completely managed by AWS. The developers should concentrate solely on the creation of the application and not on the infrastructure itself.

The most beneficial aspect of Amazon DynamoDB is that it is completely managed by AWS. The developers should concentrate solely on the creation of the application and not on the infrastructure itself.

We were building Amazon Alexa Game in which we used the DynamoDB for storing the user's data and leaderboard. Integration of Amazon DynamoDB was very smooth, there are pre-built examples are available and due to it is NoSQL, we can store any type of data without generation of the schema.

It is useful use-case by use-case. For our use case, it was the best and easiest option for the integration as well as development side. It is serverless so no need of deployment and maintenance hustle. It is easy to scale up due to the same functionality. Supports AWS Security features and just a click away for enabling it so security is good.

We are a fashion ecommerce company.
We have thousands and thousands of products in our inventory, with the use of Amazon DynamoDb it is easy and quick to fetch and insert products to the database.
Each and every information such as color, size etc is stored in the db and everything is super quick and efficient.

It is well suited for applications that will handle high traffic as it is very scalable and easy to scale.
Due to its low latency, it is well suited for application that needs real time data processing like trading application.
But if, there is structured application then i would suggest them to go with Relational database approach unlike Amazon DynamoDB as it offers nosql

From storing huge amounts of data generated by our applications to caching our data in order to increase the performance of our applications, Amazon DynamoDB helps in a vast area of our daily operations. Since it is a fully managed database service, it saves a lot of hard work on our part.

At higher request rates, Amazon DynamoDB performs smoothly. It can take big workloads with the same speed and perform equally as fast. Handling millions of queries per second is like nature to Amazon DynamoDB. And all this at a huge scale won't give problem at all.

We were using DynamoDB for storing the configuration of our webhook solution. Each integration had multiple configuration options, such as authentication mechanisms and behavior parameters. Storing all of this in a single table was not feasible, so we decided to leverage DynamoDB for the speed and flexibility it provides in this scenario.

If you are utilizing the AWS ecosystem and require a solution for handling JSON document configurations, DynamoDB is the perfect choice.

But if you're out of the AWS ecosystem you should consider other solutions.

We have high volume of data approximately 5million coming from legacy system through message queue. Those records were landed to springboot kafka but to persist data fast we tested MySQL and Oracle and there was a great number of throttling then tested Amazon DynamoDB which was super fast and without any throttling we achieved our target.

The high availability, easy to implement and secure enough to cover HIPA compliance is way to go. If you are working on data that have HIPA compliance concerns then DynamoDB is way to go.

The database is always replicated to 3 different regions seamlessly and without interrupting or slowing down the main database.

We use Amazon DynamoDB as one of the data base components of our complex environment. It was mainly use in conjunction with AWS Lambda serverless computing service. We use it as search engine index for complex data sets. What's more we create flagging functionality not double execution of some Lambda functions.

Due to Amazon DynamoDB flexible schema and key-value data models it is well suited for either serverless application or IoT services. Gaming and streaming applications with heavy user traffic can benefit from fast and flexible Amazon DynamoDB key-value NoSQL database.
Wahts more as we use it, its great for indexing other complex data base or data sets.