I like the idea, but can't love the design just yet. The information density is a bit low for me, and I'd like to be able to filter in more ways. Promising though.
"Consistency around CAP is similar to what you find in a typical ACID model - except that, now, we're in a distributed model."
I thought that consistency in ACID meant that data was always consistent with the rules of the database, whereas in CAP it means that the same data held in different locations is the same? Is that not right?
From Eric Brewer himself: "The relationship between CAP and ACID is more complex and often misunderstood, in part because the C and A in ACID represent different concepts than the same letters in CAP..."
No, the data in different locations does not need to be the same (think: quorum operations).
Consistent means that they are consistent from the perspective of the client within the rules of the consistency model. If you have sequential consistency and quorum operations, your replicas do not need to have the same data, but the view of your clients is always consistent.
I ran into this yesterday, having tried to install yeoman into a folder shared between a windows host and a linux vm.
Ended up with files which could not be deleted by any other way than from the windows command prompt using the 8.3 filenames.
An hour of swearing was enough to convince me to stop using windows for this entirely.
