Errors in Database Systems, Eventual Consistency, and the CAP Theorem

Re:Errors in Database Systems, Eventual Consistency, and the... by kingkilr on Wednesday April 07, 2010 @02:12PM (#1247972)

The C in CAP and the C in ACID are not the same C. Consistency in the ACID sense means that all constraints are met, Consistency in the CAP sense means all servers have the same data.

[ Parent | on HN ]

Re:Errors in Database Systems, Eventual Consistency, and the... by cx01 on Wednesday April 07, 2010 @02:20PM (#1247992)

I know. I actually explained this not too long ago here: http://news.ycombinator.com/item?id=1191003

But what I'm saying here is: You cannot have ACID transactions without the C in CAP.

[ Parent | on HN ]

Re:Errors in Database Systems, Eventual Consistency, and the... by dm_mongodb on Wednesday April 07, 2010 @02:21PM (#1247994)

fwiw, here is the formal version of the theorem from the gilbert/lynch proof paper:

Theorem 1. It is impossible in the asynchronous network model to implement a read/write data object that guarantees the following properties: * Availability, * Atomic consistency, in all fair executions (including those in which messages are lost).

[ Parent | on HN ]