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



Presentation: Introducing Riak and Ripple

A presentation by Sean Cribbs (@seancribbs) on Riak and the Ripple Ruby client library. Together with Kevin Smith’s Introduction to Riak you should get a pretty good idea of Riak strenght.

My notes:

Mythbusting “scalability”

  • Scalability is not a yes/no question
  • It’s a ration of benefit to cost
    • Benefits: low latency, throughput, uptime, concurrency, reliability
    • Costs: CPU, RAM, disk, bandwidth, power, hw/sw
  • scalability = bang for your buck (ROI)

What is Riak?

(the horizontal scaling bits)

  • Based on Amazon’s Dynamo (2007)
    • key-value storage
    • masterless, peer-to-peer replication
    • consistent hashing
    • eventual consistency
    • failover - quorums, hinted handoff

What is Riak?

(the document database bits)

  • store your objects as JSON (or any format)
  • link between objects (like hypertext)
  • No SQL - query with Javascript Map-Reduce

What is Riak?

(the ops-friendly bits)

  • web-shaped storage
    • store data in its original format
    • it’s just HTTP - same techniques apply
      • load balancing, proxy caches, round-robin DNS
  • no node is special - grow horizontally
  • get some sleep, fix it in the morning

Other topics covered:

  • CRUD in Riak (slide 74)
  • Links (slide 80) and link-walking (slide 83)
  • Riak Map-Reduce (slide 93)
  • Ripple (slide 132)