+1 for Mongodb on a EC2 instance instead of Dynamodb
We're transitioning off Dynamo as soon as possible as the billing structure makes it either a real headache or very expensive.
For example: if you want to make a backup of a large table or move data around, it'll either take days or cost you an arm and a leg. This is just one of many annoyances. Ever since making the decision to go with Dynamo over Mongo, I've been getting dirty looks from my team.
The set of problems where you're really struggling between mongodb and dynamodb as a choice is practically non-existent. They have hugely different characteristics and vastly different trade-offs. You might want to spend some time reading about the architecture of various databases before just picking one.
We're transitioning off Dynamo as soon as possible as the billing structure makes it either a real headache or very expensive.
For example: if you want to make a backup of a large table or move data around, it'll either take days or cost you an arm and a leg. This is just one of many annoyances. Ever since making the decision to go with Dynamo over Mongo, I've been getting dirty looks from my team.