Amazon DynamoDB Reviews

We use the solution to handle structured data. So, whenever you need to make a runtime call and send any data, you can create it. To store the data exclusively, we need to use granularity. You must integrate with Lambda to process and store the records, whether they're coming from Connect or elsewhere.

The most unbelievable feature is NoSQL. Unlike traditional SQL databases, DynamoDB doesn't require predefined schemas. You don't have to design the schema, which can be limiting in SQL databases. Additionally, in SQL databases, modifying the schema to add new columns can be confusing and must be done before adding new data. DynamoDB allows for flexibility in adding new attributes to your data at runtime without altering the schema. This makes data processing more efficient and customizable. The performance of DynamoDB is highly configurable, depending on the provisioned Read Capacity Units and Write Capacity Units that you allocate to your tables.

The solution could be cheaper.

I have been using Amazon DynamoDB for 6 years.

The solution doesn't break down.

The availability is very good. It is also scalable.

The solution is expensive.

DynamoDB is one of the services that 90% of people use on AWS.

Let's say we are developing an application using AWS. For the backend data storage, DynamoDB is the best solution AWS offers for NoSQL databases. If SQL is needed, then RDS is the way to go.

You must understand the basic CRUD operations of databases, along with the APIs. Knowing how to create a schema, determining primary and foreign keys is essential. The AWS documentation provides detailed guidance on these.

DynamoDB supports multiple areas and has good monitoring and security features. AWS CloudWatch can be used for monitoring, and third-party tools like Datadog or additional integration are available for functionality.

Overall, I rate the solution a nine out of ten.

Amazon DynamoDB is used to store data in the form of JSON. I use AWS Lambda to insert data into Amazon DynamoDB.

In a relational database like MySQL, we convert values, like name, age, or other details about a person, into tables. We directly pass the JSON value to Amazon DynamoDB, which is why Amazon DynamoDB is faster than relational databases.

The solution's efficiency and performance should be faster than other databases.

I have been using Amazon DynamoDB for six months.

I rate the solution a nine out of ten for stability.

Amazon DynamoDB is a scalable solution that can store more data than other databases. AWS manages Amazon DynamoDB, such as increasing the storage, RAM, or CPU of its actual server. We need not worry about the solution's scalability. The solution's availability is 24/7.

The solution’s technical support is good.

I previously used Amazon RDS.

The solution’s initial setup is easy.

We can deploy Amazon DynamoDB in one to two hours.

The solution was free to use one month ago, but now it is a paid service. Amazon DynamoDB is not an expensive solution.

We can use Amazon DynamoDB for both on-premises and in the cloud.

Overall, I rate the solution a seven out of ten.

We use the product as our database. It is a NoSQL database. We can use DynamoDB as our database if we don't need SQL.

The best feature of the solution is that it is a NoSQL database. Many tables make a database. When we define a table, we have to define the schema of the table. For NoSQL databases, we don't need to define it. The table accepts any input. Each row will have its own column. We do not have to define the columns in advance. We can add columns to each row and push the data. We can query as much as we want.

SQL databases exist to speed up the queries. This advantage is not present in NoSQL databases. We must query databases very fast. To help with the process, the product provides secondary indexes. Secondary indexes are a copy of the table. The table is constructed in such a way that it can be used to support one query. Whenever we query a particular item, if we give the name of the secondary index in the query, the query will be faster.

The solution supports around 20 global secondary indexes. We can just create a table without thinking about its format. When our application develops, we will have more and more queries to do. We might realize later that the initial table does not support the query and that we have to change the schema of the table. To do so, we will have to change the structure of the entire table for one query. In DynamoDB, when we encounter a new query, we can just create a new secondary index for that to an existing table. We wouldn’t have to modify the main table. The query will be fast when we query the secondary index, which is a copy of the main table. Through the production process, we don't have to be concerned about modifying the main table.

The product allows us to query for items in the UI. Sometimes when we query through the UI, it takes a long time to get the results. I would like it if the results were faster.

My organization has been using the solution for more than one year.

The product is stable. We have had no issues. We always get the data.

The solution is scalable. Around four people were using the product before. Now, only two people use it in the organization.

We were using MongoDB. It was outside AWS, and we wanted to get everything inside AWS. So we chose DynamoDB. I prefer DynamoDB over MongoDB.

The solution is deployed on the cloud. The initial setup is very easy.

If we go through the main DynamoDB, it will be a scan operation. It will scan through each record. If we set up a secondary index for a particular query type, we can get it fast. It is the fastest way to get it.

In a normal database, if we launch something into production and want to add one more feature, but the feature needs an additional query, and the existing table cannot perform the query fast, we will have to remodel the entire table. It will interrupt the process. In DynamoDB, we can just add one more secondary index and route that query to the secondary index.

If someone wants to use the solution, they should go ahead. It is as good as anything else. Overall, I rate the product a nine out of ten.

We use Amazon DynamoDB to manage our localization data.

There aren't any issues with the product. On the contrary, it has helped us build our product from zero point to the end. In addition, I like that there's no need for external configurations or DevOps engineers.

The documentation is not good enough and can be improved. There is a lot of information, and it is old and hard to find specific information. The documentation should be updated like the Firebase in Google.

It is not easy to manage. For example, uploading a certificate and resources to our GraphQL databases is too difficult because there's no user interface. You need to jump into terminal business.

We have been using this solution for two years.

We have not used technical support before.

I just used Neo4j, which is an Amazon AWS product. Unfortunately, the price is increasing daily, and it is tricky to implement things inside AWS. It's not easy, but it's doable.

The initial setup is complex, and you need to search Google to find the correct information. I rate the initial setup a four out of ten.

We used a credit from AWS for this solution. I don't remember specific details about the cost, but it is costly. I rate the price a two out of ten. I live in Turkey, and because of the currency, it is high. I think Amazon needs to create a cluster or environment in this geographic territory so we can spend in our currency and not dollars.

I rate this solution a seven out of ten. Amazon DyanamoDB has its triggers, and we would like them to simplify the process of adding a trigger without taking care of the API code. Once something has changed inside of it, it triggers a function. You can bind Lambda Function, but it's tricky because their containers are working. So, you need to know every detail about Amazon containers. So, Amazon DynamoDB creates a default and runs the function for us. So the only thing that I would be responsible for is adding our code.

My company has a fleet management system, and we primarily use DynamoDB to store location data.

I appreciate the visibility of DynamoDB, as I can observe everything on the Console. I can also monitor its operation with CloudWatch. As more data comes in, although we pay more, the product scales well. However, it can be expensive.

There is nothing that I can think of for improvements.

I have been using DynamoDB for five to six years.

Amazon DynamoDB is pretty stable. I haven't encountered breakdowns or bugs.

DynamoDB scales well. As more data comes in, it becomes more expensive, however, the scalability aspect is not a concern.

About 30% of the time, Amazon's support lacked enough knowledge to solve my problems. 

Neutral

The initial setup is straightforward.

As more data comes in, it can become expensive, however, it's a manageable cost.

I would absolutely recommend DynamoDB to others. It's easy to use, especially if sticking with AWS. 

Overall, I would rate DynamoDB nine out of ten.

We mostly use it for e-commerce data.

Any inflow of new data, whether it is new input or schema inflow, can be captured and stored in DynamoDB. Any variables or inputs can be captured in DynamoDB.

It's easier to scale than other databases.

It's serverless, scalable, and we can replicate and do blow letters. It's okay from my side.

When creating login credentials, we can make a security setup while using DynamoDB.

It has a different schema type than other databases. DynamoDB has a separate schema.

It is a schema-less, NoSQL database. When connecting to other services, we need to sort and code the data. We need to especially monitor the coding of the data. There will be some minor changes to normal coding.

I have been using it for two years. 

I would rate the stability a seven out of ten. We faced some configuration issues.

We mainly need to know the configurations and settings. They need to be customized before setup can be done.

We are a small company; only four developers use it.

I would rate the scalability an eight out of ten. 

AWS technical support is very friendly and looks out for the business to continue. They will support you based on your support ticket.

Positive

I have used Azure. It was for a previous project.

For deployment, we use libraries. If you want to create a library, it's basic functionality. We can call it by integrating with any Python library. We can deploy it very quickly and easily.

Compared to MongoDB, we can set up DynamoDB within half a day.

AWS handles the maintenance.

It's pay-as-you-go. You pay for how much you use and store. We can also make automatic backups and use replication for the database. It is suitable for high-performance applications.

It's on a monthly basis. So it's a subscription.

We use it for support services, so we subscribe to it only when needed. So, the pricing can vary. 

I would rate the pricing an eight out of ten. 

I can recommend AWS, especially for enterprise and retail-level customers. 

Overall, I would rate it a seven out of ten. 

We use Amazon DynamoDB because we require a non-relational database for a variety of brands.

For example, we have extensive experience with relational databases. If you use Dynamo to implement a large project, it will help you implement it faster and perform faster searches. It's good because I feel, the JSON format makes it easier to read.

The most valuable feature of this solution is the non-relational database.

If you have no prior experience with this type of non-relational database, the syntaxes, implementation, or understanding may be difficult.

I have been using Amazon DynamoDB for one year.

I am working with the latest version.

Amazon DynamoDB is quite stable.

Amazon DynamoDB is a scalable solution.

We have 160 users, in our organization.

We need to build a better solution using this database. Perhaps for future items. That was a great experience.

I would rate the technical support a four out of five.

Previously, we used CatalinaDB. It is very similar.

If you don't have any prior expertise, it may be rather complex.

We only require one person who has knowledge of databases to maintain this solution.

The deployment was done in-house.

We have seen an ROI, but the pricing is actually determined by the clients you implement.

It is a little expensive. 

It is dependent on the license you use. The license we now have is for the consumption of reading. It's around $80 each month, or more.

We tried to implement certain schemes or determine what is the best way to implement the project. We discovered that Dynamo was better.

Have database experience not just in relational databases, but also in non-relational databases, as well as AWS or configuration experience.

I would rate Amazon DynamoDB a nine out of ten.

We use this solution for two main purposes. The first is for the IoT-H devices to collect data and push the collected data to the DynamoDB. The second aim is to use the Terraform integration for the GS. This solution supports 25 users. 

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

I have been using this solution for more than two years. 

This is a stable solution. In the last three years, I have not encountered any issues. 

This is a scalable solution. 

We make use of the paid version of support and do not usually wait more than 40 minutes to be assisted via email or live chat. I would rate support a five out of five. 

Positive

The initial setup is not that easy. It requires at least one mid-level DevOps engineer to understand both the company requirements and also the AWS capability in order to meet them. I would rate the initial setup a four out of five. 

I would rate the pricing for this solution a four out of five. 

I would rate this solution an eight out of ten.