Re:How NoSQL forced the evolution of a scalable relational d...
by qaq on Friday July 13, 2018 @05:29AM
(#17521564)
Spanner is CP I think the A part comes from reliability of google network infrastructure which is not part of DB system's design per se.
[ Parent
| on HN ]
Re:How NoSQL forced the evolution of a scalable relational d...
by logophobia on Friday July 13, 2018 @05:39AM
(#17521608)
I think I misunderstood that yes.
https://storage.googleapis.com/pub-tools-public-publication-....
TLDR: It's technically CP, but google claims partitions are so rare people can assume it's CA as well (99.999% available).
I assumed TrueTime bypassed the CAP theorem, but apparently that's marketing bs. It's to ensure something called external consistency, which is important if you want to take consistent snapshots over a distributed system.
Re:How NoSQL forced the evolution of a scalable relational d...
by majewsky on Friday July 13, 2018 @09:00AM
(#17522536)
Semi-related soapbox: Can we all please stop saying "CAP theorem" and instead say "CAP rule"? The formulation of this supposed theorem is so vague that it can neither be proven nor disproven.
Re:How NoSQL forced the evolution of a scalable relational d...
by logophobia on Friday July 13, 2018 @11:22AM
(#17523674)
It was proven in 2002, has a formal definition, so I'm going with calling it a theorem. Maybe this'll help: https://mwhittaker.github.io/blog/an_illustrated_proof_of_th... ?