Cassandra is an open source, highly scalable distributed database that's rapidly gaining momentum in the NoSQL community. It brings together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model to provide a unique data storage solution that is suitable to a wide variety of use cases.
Professor Eric Brewer's CAP theorem states that a distributed system design can offer at most two out of three desirable properties: Consistency, Availability, and Partition Tolerance. So, how do you provide consistency when your distributed system's primary requirements are availability and partition tolerance?
In this talk we'll introduce eventual consistency and the four strategies that Cassandra uses to provide it, while still maintaining high availability:
* Read Repair
* Hinted Hand-off
1st–4th June 2010