Amazon SimpleDB vs. Riak

Well suited for: Games, Chat rooms, real time software like corporate events, marathons and so. Anytime and anywhere you could use a NoSQL DB you should think of SimpleDB.

As an arduous AWS user, Amazon SimpleDB easily integrates with EC2 and other AWS module; and if you are not an AWS user, you also have a fantastic tool that will solve the problem for which you are focused.

Incentivized

Riak is well suited to applications such as:

Transaction logging e.g. financial transactions and/or exchange rates.

Storing time series data, especially IoT.

Storing massive amounts of data e.g. corporation wide backups, data lakes etc.

A fully s3 compatible replacement for Amazon s3 ensuring data privacy.

Riak is not as well suited to:

Traditional RDBMS functions, especially those that join the outputs of one or more queries together to produce the desired result.

• Flexibility
• Easy to learn and use
• AWS integration

Incentivized

• Highly available: If nodes go offline for any reason, the system still operates.
• Highly scalable: There is a minimum of 5 nodes, which can handle a lot by themselves. When scaling is required, it can be done easily, with minimal to no downtime on large scales.
• Very fast searching: Riak has SOLR indexing built-into the core product, which makes querying for data very fast.

Incentivized

• Non AWS environments
• Strict storage limit (but well we have DynamoDB for storage issues)

Incentivized

• Deletes!!! We've seen on numerous occasions where Riak has "resurrected" deleted data. We've worked with Basho numerous times and tried multiple changes to the way we interact with Riak to prevent the problem but it still remains. The deletes seem to reappear weeks, even months, after the delete was issued. We've had to work around this issue by providing a "deleted" flag for all data objects stored in Riak. Thus, we do no delete but simply flip the flag. Excess baggage we would really like to not have to worry about.
• Search. Currently there's no way to tell what data you have in Riak without already knowing a particular bucket/key. There is a way to list the keys for a given bucket but due to performance implications, this is not a viable method to lookup data. Especially when you have a large amount of keys in the bucket.

Incentivized

Right now, I'm on a project where we need databases that can run on embedded systems. Riak isn't necessarily the best fit for that scenario. But when we need a clustered database, that's where we'd start considering Riak.

Incentivized

Despite Basho going bankrupt and the project becoming fully open-source, community support is reasonably good, albeit a little slow at times. Paid enterprise-grade support is also available from former Basho engineers but the same company also contributes to the community support for free for basic questions or specific knowledge areas.

It integrates beautifully with AWS. In some projects we use SimpleDB while we use DynamoDB for others, according to the characteristics of the project. If the infrastructure is AWS, we always think of one of them.

Incentivized

Because of the RESTful HTTP interface, the consistency model, and because of the catalog-driven data model, Riak was an easy win over Redis and Memcached.

Incentivized

• Reduced database administration time
• Reduced data model analysis time
• Lower cost of resources in projects in general

Incentivized

• Riak has been a key part of our company's build process for our client's search backend. It is valuable for is in that it provides a reliable way to view the current search index.

Incentivized