41. Name: Dynamo Created: 2007, Amazon (proprietary) Implementation: ? Distributed: Yes Replication: Multiple Servers CAP: AP API: ? Key / value store
42. Name: Membase Created: 2010, sponsored by Zinga Implementation: C / C++ / Erlang Distributed: Yes Replication: Multiple Servers CAP: CP API: Memcached API, JSON Key / value store
43. Name: Voldemort Created: 2008, LinkedIn Implementation: Java Distributed: Yes Replication: Multiple Servers CAP: AP API: Java Key / value store
44. Name: Redis Created: 2009, sponsored by VMWare Implementation: C Distributed: No Replication: Master / Slave CAP: CP API: Various Languages Key / value store
45. Name: Azure Table Storage Created: 2008, Microsoft Implementation: ? Distributed: Yes Replication: Multiple Servers (DFS) CAP: CP API: .NET API, JSON Key / value store
46. Name: Riak Created: 2008, Basho (from Akamai) Implementation: Erlang Distributed: Yes Replication: Multiple Servers CAP: AP API: JSON Key / value store
Atomicity. All of the operations in the transaction will complete, or none will.Consistency. The database will be in a consistent state when the transaction begins and ends.Isolation. The transaction will behave as if it is the only operation being performed upon the database.Durability. Upon completion of the transaction, the operation will not be reversed.
Consistency. The client perceives that a set of operations has occurred all at once.Availability. Every operation must terminate in an intended response.Partition tolerance. Operations will complete, even if individual components are unavailable.http://www.cs.berkeley.edu/~brewer/cs262b-2004/PODC-keynote.pdf
Basically Available. Supportingpartial failures without total system failure.Soft state. The state can be inconsistent for a given period of time.Eventual consistency. After some time all replicas will have consistent data.For a given accepted update and a given replica eventually either the update reaches the replica or the replica retires from service