Amazon DynamoDB Reviews

Since Amazon DynamoDB is a serverless NoSQL database, we are using it to develop an application that uses a NoSQL database.

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

Amazon DynamoDB has a very complex configuration if you go very advanced.

I have been using Amazon DynamoDB for the past two to three months.

We are very much satisfied with Amazon DynamoDB's global tables feature. It was very easy for me to learn to use Amazon DynamoDB. After one week of upskilling, I was able to query and use the solution. The solution has a very user-friendly interface. If you don't know about queries, you can filter out data with the interface without writing complex queries.

Our company decided to use Amazon DynamoDB because it is a serverless, NoSQL database. Amazon DynamoDB has a very complex configuration if you go very advanced. So, start with the basics and use PK and SK only. After that, you can jump to search indexes. If you have some advanced use cases, the configuration might have some complexities. Amazon DynamoDB has good scalability, and it is very fast for querying.

Overall, I rate the solution ten out of ten.

DynamoDB is suitable for a wide range of applications, from small-scale projects to large-scale and high-traffic applications. Amazon DynamoDB is a high-performance managed service, and AWS fully takes care of the operational parts, including hardware, setup, and maintenance.

Amazon DynamoDB is a fully managed service by AWS, and it is designed to provide fast and predictable performance.

The solution's backup and restore could be improved to be able to utilize batch operations.

I have been using Amazon DynamoDB for more than two years.

Amazon DynamoDB is a stable solution.

Amazon DynamoDB is a scalable solution. More than three people are using the solution in our organization.

The solution’s technical support is good.

The solution’s initial setup is easy.

Amazon DynamoDB is a cheap solution.

Amazon DynamoDB automatically publishes AWS CloudWatch metrics that provide information on health and performance, read-write capacity, system errors, and conditional check fail requests. It is easy for somebody to learn to use Amazon DynamoDB. I would recommend the solution to other users.

Overall, I rate the solution ten out of ten.

I use Amazon DynamoDB for EMR automation for EMR to run. Right? We have to configure everything on time since we have configurations on Amazon DynamoDB.

We mainly use Amazon DynamoDB, like a session DB kind of solution. Also, the solution's pricing is really nice. So I use it because I don't have to pay for it throughout. It is based on the usage that I have to pay. So that is where MySQL, I had to pay 24/7. With Amazon DynamoDB, I had to pay only when I used it and the amount of data I had stored. So, it reduced my cost since it was much cheaper as compared to MySQL.

The solution's interface is the biggest challenge because if you want to access DynamoDB, you need an AWS account. So, you need to be logged in to the AWS console and can only make changes from there. So, if there's, like, any other DB, like, whether it's Redshift or any other service that shows us Spectrum, Athena, or anything they provide, we can connect it through an external client. I don't need to be logged in to the AWS console. That is one thing where it restricts me, and as of today, I've restricted its access to four people who can make the changes in the product or who can monitor or directly log in to DynamoDB and check what has been configured, what is working, what is not working. But if it was accessible, like any other DB, I could have just given them more people to read permission, and It would have been easier for me to maintain that.

As of now, I'm using it as a configuration DB and not exactly using it for transactions or storage since, for such purposes, I depend on Redshift.

I have been using Amazon DynamoDB for a year and a half.

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

Scalability-wise, I rate the solution an eight out of ten. Ideally, it is supposed to be instantaneous after we make a request, but it wasn't since I had to, like, it took me some time to increase the size of Amazon DynamoDB. However, the opinions from my other colleagues and ex-colleagues indicate that it is faster. Based on my experience, I haven't had a similar experience as my colleagues.

I don't have direct users on Amazon DynamoDB. It's applications that are accessing it now. I don't even have multiple applications such as workflow and big data. I have probably a hundred-plus workflows that are running on a daily basis.

I have never had any issues with AWS support since they have been fast and helpful, and I have them on my speed dial. So, I can just call them and reach out to them.

Previously, I was using Cloudera platform, where we were using MySQL as a configuration repository because we have been building big data pipelines and other things. So, what happens is that queries and other things that we have to fire on Redshift DB or maybe in Hudi or Kudu, all these DBs that are part of the Cloudera stack, we used to store all the queries in MySQL. We then decided to move out of Cloudera and go to EMR. For us, the easiest option was to go for MySQL, but it is not that closely integrated with AWS EMR. So it would have been an outside product being introduced or coming into our environment. Hence, we decided to go with DynamoDB, as it is an AWS product.

The solution's initial setup was simple.

I got myself involved in the process.

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.

I don't think I will be able to compare DynamoDB with other solutions in the market since there's a huge difference between any other DB that I have used and DynamoDB. I will not be in a position to give an objective view.

Overall, I rate the solution an eight 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. 

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. 

It is a NoSQL product. We can write what we want, and it will be stored. We need not worry about the structure. If we want to use a database for small use cases, we can use DynamoDB. If the CPU is high in a day, I can check what time it went high, how many people came into the site, and understand the database usage. Whenever the CPU is high, I send all the data to my database and analyze why it is high so that I can minimize the usage accordingly.

If we want to add another field, we can do so easily. It won’t show any errors. There is no need to migrate. Data modeling is easy. Whatever language we use with the product, we must check how to connect and write it. We must use some DynamoDB functions. I use the product with Lambda.

The pricing for larger databases is higher.

I have been using the solution for one and a half years.

We did not have any issues with the tool’s stability. We did not face any issues with bugs.

The tool’s scalability is good. I rate the scalability a nine out of ten.

The initial setup is straightforward.

We mostly use PostgreSQL.

I have used Amazon RDS. We do not use DynamoDB much. I will recommend the product to others. If we want a small database, Amazon DynamoDB is a good choice. We can use it for larger use cases, too. However, pricing might be high if we opt for the larger database. Overall, I rate the tool a nine 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 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.