Amazon DynamoDB Reviews

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 host the cloud version of our software, ENSUR by DocXellent, on EC2 instances with fifteen separate installations currently.

These low-cost, flexible, and scalable VMs are an excellent value for the service they provide.

We also utilize CloudWatch monitoring, the Simple Notification Service, and the VPC solution for VPN connections for us, and for our clients, to these instances.

Previously, our product was exclusively sold as an on-premises solution. Once we decided on AWS for a cloud hosting platform, we were able to increase our sales dramatically. Within less than two years of offering this option, cloud hosted sales now make up more than 50% of our new business.

AWS is forward thinking and always adding new features. I generally cannot think of an area of improvement.

To be honest, AWS and their people know way more about the hosting and infrastructure needs of software developers than me and my team. I can’t think of any features that that could additionally add.

If I were to pick on one area to improve and an area in which they are not equal to or superior to the competition, I would say the user interface. It is far more simplistic that Azure’s slick presentation.

Of course, that is by choice, like the Amazon experience. But there are instances where the next step is not as logically presented as in Azure.

I still maintain that AWS is the unquestioned market leader in regards to features offered and is always introducing new ones in response to what their customers ask for.

They also are leaders in price, ease of use, and support, making them the obvious choice for my company’s cloud IaaS provider.

I have used Amazon AWS for three years.

There have been a couple of well-publicized instances of non-availability, but I think overall downtime of a few hours per year is acceptable.

The biggest problem is that everybody knows about downtime because of how public AWS’s failures are with their high-profile customers, who make news with their downtime.

We have had no problems with scalability.

I would give technical support a rating of 10/10. AWS stands for AWesome Support! They know way more about problems than I do and often patiently teach me while solving an issue.

We occasionally use Azure, alongside AWS, because we have a monthly credit from Microsoft. But AWS was first and all our commercial accounts are on AWS.

I was able to setup a prototype of our application by myself in half an hour. Since then, whenever I need to do something new, rather than read a whitepaper, I just call support and they walk me through it. This is part of the support they happily provide AND without griping about me not trying it by myself first.

You don’t need to look anywhere else. AWS is the leader in price and features, so why mess with success.

We evaluated Azure, Google, Rackspace and several smaller, now extinct companies.

I have set up Amazon DynamoDB and started using it with my product for data insertion, creation, reading, testing, and configuration.

Amazon DynamoDB is a NoSQL database that stores unstructured data and provides high performance.

I initially faced issues with the solution's stability, performance, and security.

I have used Amazon DynamoDB two to three times.

I rate the solution’s stability a seven to eight out of ten.

I rate the solution an eight out of ten for scalability.

The solution’s technical support is good.

The initial setup of the solution is average, and it is neither easy nor difficult. You do need to have some knowledge and experience to set up Amazon DynamoDB.

Given the services and benefits provided by AWS, the solution's pricing is average.

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

I integrate Amazon Connect with Amazon DynamoDB for the database.

Amazon DynamoDB is serverless and fast, and we can use different keys along with it in our code. Amazon DynamoDB can accommodate any number of datasets. It is better than the RDB (relational databases). We can use the primary and sort keys to get any sorted data, which is good. The solution is easy to use.

Anyone with AWS Lambda knowledge can easily integrate and use Amazon DynamoDB. The solution supports all languages.

The solution would work fast if a contact center is in the same region.

I have been using Amazon DynamoDB for four years.

We haven’t faced any issues with the solution’s stability.

We can scale Amazon DynamoDB as much as we can.

I rate the solution’s scalability a nine out of ten.

We can integrate Amazon DynamoDB with other AWS services in our architecture with a simple function. I would recommend the solution to other users.

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

The solution makes it simple to manage the database.

The most valuable features of the solution are its price and stability. The solution can handle all our payloads and workloads. The solution's documentation is very clear. Amazon DynamoDB is a good solution that is easy to configure. Data security is one of the main reasons we use the solution.

The solution's initial setup is a bit complex if you want it for something more specific.

Amazon DynamoDB is a stable solution, and I haven't faced any issues with stability.

More than 1,000 users are using the solution in our organization.

I've used MongoDB. I like both Amazon DynamoDB and MongoDB because they take different approaches. However, if I have to recommend one over the other, I will recommend Amazon DynamoDB.

The solution's initial setup is a bit complex if you want it for something more specific. However, it can be straightforward if you need it for something basic.

The solution's pricing is good, and it's not expensive.

The solution has helped us save 30% of our costs. Our main project is automation to help businesses communicate with their clients.

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

We use the solution to emulate MongoDB for the document database.

The solution is useful for storing JSON documents. DynamoDB is a platform as a service. We don't have to administer the tool. We did not face any challenges while integrating the product with other services.

We use the document database. The primary key is quite slow. The free tier is quite hard to use.

I have worked with the tool for three years.

The tool is stable.

We are satisfied with the scalability of the tool.

The deployment is quite easy. The deployment takes a minute. We need only one engineer to install the solution.

The ROI is very good at the beginning. However, it gets expensive if we use it a lot.

I rate the pricing a six out of ten.

DynamoDB and Cosmos DB are more or less the same. My preference depends on the cloud I am working on. However, I prefer Cosmos DB because I have used it more.

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