Thursday, February 19, 2009


What is the problem? Is the problem real?
Highly available, partition tolerant, high performance value-key store.

What is the solution's main idea (nugget)?
Use various well known distibuted systems techniques to build a flexible storage solution.
-consistent hashing (sounds like Chord)
-object versioning (sounds like BigTable)
-"sloppy quorum" (from talk) for consistency
-"decentralized replica synchronization protocol"

Why is solution different from previous work? (Is technology different?, Is workload different?, Is problem different?)
Their demands are slightly different than the related work (e.g. Chord), most of which they build off of. They do it at scale and it really works, and is in production!

How is this different from S3? - provides control over availability/performance tradeoff

No comments: