Amazon DynamoDB Reviews

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.

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. 

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.

I work in the cloud automation domain. I used the product to store data related to automation. We had our own website. We use the product to manage automation. I also used it to store user information.

The solution is very simple to use. It is a NoSQL database. The UI is good. DynamoDB Streams is an amazing feature. If there are any changes in the DB, it will automatically trigger the workflow. The GUI is awesome.

I have used the solution in the past year.

I rate the tool’s stability a ten out of ten. It worked perfectly for us.

I rate the tool’s scalability a ten out of ten. We had more than 500 users.

I used MongoDB a very long time ago.

The initial setup is easy. The documentation is good. The deployment could be done within minutes.

The solution is cheaper than Cosmos DB. If an organization doesn’t have much data to store, they can use the solution for free.

It is a good investment. We were able to use it in automation. It was easy to use. Even the new joiners were able to use it effectively. All our automation was effectively stored, and we could build the dashboard out of it to present to the higher management. Anyone who wants to explore a NoSQL database in the cloud must use DynamoDB. Overall, I rate the product a ten out of ten.

My use case is user data management.

It is fairly straightforward. The best part is the scalability, the response performance, and scalability part. I didn't like the API extremely well, but it was okay. 

Moreover, the system is pretty well documented, which is important. And it's observability. That's okay.

Data integrity across availability zones would be a valuable addition. 

Currently, DynamoDB provides eventual consistency across availability zones, but strong consistency would be beneficial for certain use cases.

There is room for improvement in the pricing. A more tiered pricing structure would better accommodate different usage patterns. Similar to leasing a car versus buying it outright, there should be options for those with lower or higher usage volumes.

I have been using this solution for three years. 

It is stable enough.

This is a backend system. So it can be hundreds of thousands of users because it's not like a user interface type thing.  So, it serves hundreds of thousands of real-world users.

It is a highly scalable solution. 

Never used the support. I got all the information from the documentation. 

I've worked with NoSQL databases like Redis and Amazon Keyspaces in the past.

We switched to DynamoDB because it is SaaS. We didn't have a dedicated team to maintain our database infrastructure.

Technically, Redis is better than DynamoDB is quite capable. However, it requires less maintenance compared to other NoSQL solutions.

I tried Step Functions, but it would be too pricey if I used it too much. So, I didn't stick with it. For low volume, the peanuts work. For high volume, they become expensive.

I just did play with it and then made a forecast and said no.

We just picked Amazon DynamoDB because it did the job, we wanted to do. I don't find it complicated. We use it. It's pretty straightforward.

It is SaaS from Amazon, you just use it. You don't install anything. It could you could install it if you want. Like, I didn't, but I never used that. 

It is a service from Amazon. So that's one of the benefits; you just use it. There is no maintenance required. 

For our use case usage, DynamoDB's pricing was okay. However, for high-traffic applications, the pricing structure becomes less attractive.

It might not be the best choice for high volume. DynamoDB's billing is based on usage, not a fixed subscription fee. The invoicing is done monthly, but you only pay for the resources you consume.

There are no additional charges for support or other services. You pay solely for the resources you utilize.

My role is a solution architect. So, basically, we play with what we have at hand with what's the company strategy. We're more like Jokers. We play with whatever is the context, not necessarily being like, "hey, I'm an Amazon guy. I only do Amazon." It's mostly into building the software rather than using off-the-shelf stuff. So, we just built what we needed about VPMs in other companies.

For simple, straightforward use cases, I would recommend it. And for whatever decent volume of usage means for each company, I wouldn't recommend it for a tenth of thousands of transactions per second.

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

It does the basic stuff. It's an efficient resource, just like a special database.

For us, we are using DynamoDB to store the log credentials or the token, specifically. So that's the use of the service for us.

Speed is the most valuable feature. The speed to store and retrieve data from it.

It would be nice to have some AI features in DynamoDB.

I have been using this solution for around eight months. We don't use the latest version. 

I would rate the stability a ten out of ten. It's very stable.

I would rate the scalability a nine out of ten. Around 50 to 60 users are currently using this solution in our company. We use this solution every day. 

However, we don't plan to increase the usage of the solution because we use it to restore some services when they are deployed.

We were testing different services. We used RDS. We switched to this solution for the necessity of this service. The service was changed, and we needed to create a different architecture for the application.

We did not use AWS CLI or the console to configure the services, so it's easy to do all we need.

So, it was easy to set up DynamoDB. I would rate my experience with the initial setup a nine out of ten, where one is difficult, and ten is easy. 

It took a couple of minutes to deploy it. 

We always use Terraform or another EAC tool to create a resource. We never deploy a resource using the console.

One person is enough for the deployment and maintenance of the solution. 

I would rate the pricing a four out of ten, where one is cheap, and ten is expensive. The price is cheap. It is a cheap service. 

There are additional costs for DynamoDB like the replication and backup configuration.

It's a good service for all kinds of enterprises.  

Overall, I would rate the solution an eight out of ten.

We are using Amazon DynamoDB for our company for multiple service database management.

One of the most valuable features of Amazon DynamoDB is it can handle unstructured or semi-structured data.

Amazon DynamoDB could improve by being more robust, having a better user interface and data management. Additionally, there is some limited functionality compared to other solutions, such as MongoDB.

In an upcoming release, it would be beneficial to show spatial data on the interface. There would is a very important metric for our company.

I have been using this solution for approximately two years.

I have found the solution to be stable.

The solution is scalable.

The technical support has been good. However, there should be more local support for our company that is international, this would allow for better communication.

We used MongoDB previously and I found it more powerful.

The initial setup is very easy because DynamoDB is from Amazon.

We have evaluated other solutions.

I would recommend anyone looking to implement any software to understand the needs of their business and do a purpose analysis to determine if the software fits their use case. No matter how good a solution can be if it does not fit the purpose of the business it will not be helpful.

I rate Amazon DynamoDB an eight out of ten.