Overall Satisfaction with Amazon DynamoDB
We used DynamoDB both alone and in combination with AWS Lambda functions. We used DynamoDB tables to store client data and combined them with DynamoDB streams to trigger lambda functions every time the table changed. This allowed us to run functions synchronously. Another use case was to run lambda functions at a specified UTC time zone, which was again stored in DynamoDB tables.
- Storing of Data.
- Running lambda functions to synchronously run jobs.
- Run asynchronous jobs.
- Store inconsistent data.
- It is hard to combine them with lambda functions if the job to be run will take longer than 30 seconds.
- It has some inconsistent behavior when fargate containers are involved.
- DynamoDB has been very effective for cost savings.
- Easy to combine with other AWS services, which is both easy to develop and maintain.
- Scalability is not an issue.
- Well-illustrated metrics.
- Amazon Redshift and Amazon Relational Database Service (RDS)
DynamoDB is slightly different than both the above-stated DBs, with RDS being a relational database and Redshift being a data warehouse used for heavier jobs and analytics and vast data. DynamoDB lies in between both, with it being a no SQL base that can relatively store inconsistent data similar to Redshift, but Redshift is far better in analytics.
Do you think Amazon DynamoDB delivers good value for the price?
Yes
Are you happy with Amazon DynamoDB's feature set?
Yes
Did Amazon DynamoDB live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Amazon DynamoDB go as expected?
Yes
Would you buy Amazon DynamoDB again?
Yes