|
|
|
|
|
by andras_gerlits
830 days ago
|
|
It's clear for everyone that if you define Consistency via Linearizability, CAP-like problems will apply, as you're necessarily creating original information on a potentially remote node. That's not the issue. The issue is that people in practice almost never use Linearizability for their Consistency, for example I don't know of a single SQL-implementation that does full linearizability (or Strict Serializable, same difference). So the industry already means something totally different from CAP's definition, and for those consistency-levels CAP doesn't apply. In fact, I present a technical series of arguments here how you can overcome these limits in practice:
https://medium.com/p/5e397cb12e63 There's a specific section about CAP in the end, but I talk about node-loss. replication, strong consistency and all the others also. |
|