Is there a concise document somewhere that explains why one would choose Riak -- i.e., what unique features or characteristics -- over, say, Cassandra or another DHT-style key/value store?
Mozilla's "Test Pilot" user testing system uses Riak. The Mozilla Metrics blog explains why they chose Riak, with comparisons to Cassandra and HBase:
http://blog.mozilla.com/data/2010/05/18/riak-and-cassandra-a...
Re:Riak 0.12 Released
by japherwocky on Tuesday July 20, 2010 @05:23PM
(#1533487)
Heroku actually published a really good blog post about this today.. it was on the frontpage earlier:
http://blog.heroku.com/archives/2010/7/20/nosql/
Riak's nice for redundancy and high availability stuff, and scales dynamically by adding instances.
May be a bit dated but right from the horses mouth: http://wiki.basho.com/display/RIAK/Riak+Comparisons
"Riak is a Dynamo-inspired key/value store that scales predictably and easily. Riak also simplifies development by giving developers the ability to quickly prototype, test, and deploy their applications
A truly fault-tolerant system, Riak has no single point of failure. No machines are special or central in Riak, so developers and operations professionals can decide exactly how fault-tolerant they want and need their applications to be."