Replication. Partitioning. Relational databases. Bigtable. Dynamo. There is no one-size-fits-all approach to scaling your database, and the CAP theorem proved that there never will be. This talk will explain the advantages and limits of the approaches to scaling traditional relational databases, as well as the tradeoffs made by the designers of newer distributed systems like Cassandra. These slides are from Jonathan Ellis's OSCON 09 talk: http://en.oreilly.com/oscon2009/public/schedule/detail/7955
33. *
Distributed databases
• Data is automatically partitioned
• Transparent to application
• Add capacity without downtime
• Failure tolerant
*Like Bigtable, not Lotus Notes
34. Two famous papers
• Bigtable: A distributed storage system for
structured data, 2006
• Dynamo: amazon's highly available key-
value store, 2007
35. The world doesn't need another
half-assed key/value store
(See also Olin Shivers' 100% and 80%
solutions)
36. Two approaches
• Bigtable: “How can we build a distributed
database on top of GFS?”
• Dynamo: “How can we build a distributed
hash table appropriate for the data
center?”