Amazon DynamoDB vs Riak

• Speed of data inserts.
• Quick setup of tables and integration into code.
• Automated system management

Read full review

• Consistency model is highly distributed, so uptime of our documents is always available.
• Simple to use RESTful interface, which was easy to access from our Java application.
• Data model using catalogs and indexes was simple, making it easy to store and retrieve our statements.

Read full review

• Ease of use, I had to search several non-Amazon tutorials to figure out setup.
• Integration into RDBMS would be a great improvement. Currently to move data around you have to export it and reimport into your destination. You could use Amazon Data Migration services - but not very straight forward.
• You only have once instance. If you want to group tables into a "database", you cannot do that.

Read full review

• When the index definition changes, reindexing takes an extremely long time.
• Support (both paid and community based) is very very lacking.
• It is expensive to run.

Read full review

• Scalability out of the box
• No server maintenance
• Infrastructure comes for "free"

Read full review

• Riak has had a positive impact in the fact that it is still a very fast data store and can scale very well over time.
• Riak has had a negative impact as it is one of the most expensive pieces of our architecture.
• Riak's SOLR engine failed us at a critical moment which seriously hurt the company. Our use case is very different than the norm, so I don't expect this to affect most people.

Read full review