DynamoDB works great for small development team
August 19, 2016

DynamoDB works great for small development team

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Amazon DynamoDB

DynamoDB is used by IT department in our organization. It is used when we need a no sql database and are using MySQL as a relational database. DynamoDB provides high speed read and write so we use it where we have heavy read and writes in order to make our page faster. This is helping to make our application faster.
  • No need to worry about hosting and ease of scaling and operations
  • Distributed and flexible as Amazon DynamoDB does not have a fixed schema
  • Based on load, options to increase throughput
  • 64KB limit on row size and 1MB limit on querying
  • Increasing throughput is expensive
  • Secondary indexes are not supported
  • For our small team, it has been great in aspect to cost as we save time of operations
  • This provided us fast read and write for simple queries
  • When we have complex logic and queries, we are unable to use it
While evaluating Cassandra, PostgreSQL, MongoDB and DynamoDB we found Cassandra and DynamoDB being well suited for us. At the same time we didn't have the luxury of large team or devops so it came down to Amazon DynamoDB. As a small team we are glad to go forward with this product since we save lot of time in maintaining it.
There are many factors that will make us renew Amazon DynamoDB. Firstly we have designed our existing application based on DynanoDB and secondly we will to continue to avoid hosting responsibility of another database. Our REST API deal with JSON object hence leads us to an ease of pushing to DynamoDB with less modification.
DynamoDB is well suited when you have small development team and want ease of scaling and operations. Since it is hosted by Amazon, it provides a fully managed service. It provides great read and write for simple queries. When you have complex queries, I think this is not well suited. We need to remember this is not suited for a relational database.