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
Great scalability </li></ul>Horizontal <br />Vertical<br />Columnar database<br />
<ul><li>Unusual data model</li></ul>Key Space == Database<br />Column Family == Table<br />Columns and Super Columns<br />Super Column == array of Columns<br />Column == Tuple<Key, Value, Timestamp, TTL><br />Columnar database<br />