For example, any database cannot provide availability if all of its replicas are offline, which has nothing to do with
partitions. Such a multi-replica outage should be very rare, but if partitions are signi cantly more rare, then you can effectively
ignore partitions as a factor in availability.
For Spanner, this means that when there is an availability outage, it is not in practice due to a partition,
but rather some other set of multiple faults (as no single fault will forfeit availability).
(edit): I have thought about it some more, and this article really annoys me. It reads like marketing material: "CAP doesn't apply to us because we are Google, bitches."
There is an argument there, but I think the way Brewer makes the argument is really weak. I would much rather them say: "We have built a really great CP system. Also, because we are Google we are capable of 99.99958% uptime, so you really don't need to worry to much about tiny edge cases where you will lose A."
In these types of scenarios, different sections of the system are still working as normal, and each have a different view of the network of available nodes.
In a scenario where a set of homogeneous nodes in a system is split in two, both are equally 'available' and so the system as a whole has to decide what to do in that scenario. If both sides present themselves as available then they will be making decisions based only on interactions with half of the nodes in the system and their view of the system as a whole will start to drift apart.
This is bad because at the point where they get reconnected again they may well realise that the system as a whole is now not internally consistent. If you think about a distributed database, then you can start to having conflicting commits and now your DB is FUBAR.
You are right in thinking that from the point of view of a partition that it can't know if the rest of the system is just partitioned away or has crashed and will never come back.
But what that simplifying assumption is saying is that if you can ensure that you are much much more likely to have the nodes go down completely rather than actually be partitioned, then things are easy because you don't have to consider diverging system views and how you might re-integrate them.
Or something like that, I ended up writing more than I was planning!
Maybe you are on the losing side of a split, and there is a set of nodes out there that can make quorum.
Or maybe 51% of the nodes crashed and what you see is all that is left of the cluster.
Whatever you decide, it has to work for both those possibilities.
So are you interpreting Brewer as saying, in practice we never have a split. Just assume what you see is all there is of the network. However, Spanner is a CP system. If you are willing to assume you will never need to merge inconsistent data, wouldn't you go for AP?
What he's saying is that it's strictly CP, as it will handle partitions (there's a section further down the paper describing how it would be handled). But as P's hardly ever ever happen, because Google, then it's pretty much CA (always consistent and available).
So yes, for all intents and purposes, he's saying "Yeah, CAP does apply but we're so good we can make P 'go away'."
Note that in both CockroachDB and Spanner a cluster contains many independent and overlapping replica sets. The data is broken down into "ranges" (to use the terminology of CockroachDB; Spanner calls them "spans"), each of which has its own replica set (typically containing 3 or 5 members).