ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close
Friday, 13 July 2012
‹ Back

Why We Chose Riak

About:
,
,

Lei Gu about the 9 reasons that made them chose Riak:

  1. Ever-Evolving Object Model
  2. High Availability and Multi-Data Center Support
  3. Free Text Search
  4. Adjacency Link Walking
  5. Secondary Index Support
  6. Multi-Tenant Support
  7. Ad Hoc Query Support Through MapReduce
  8. Performance
  9. Operation and Monitoring Support

These are a lot of good reasons.

Original title and link: Why We Chose Riak (NoSQL database©myNoSQL)

via: http://2rdscreenretargeting.blogspot.com/2012/07/why-we-chose-riak-as-persistence.html