Unless you put all 12 witnesses on a single machine you have to deal with the following situation:
Blue balls are picked by 4 witnesses as the main chain, green balls are picked by other 4 witnesses and there is another version picked by the remaining witnesses (it's not shown to emphasize that noone can have a complete view of the DAG). Under high load
every witness will pick its own main chain because none of them will see the whole DAG. The chance of that is high because
In normal use, people mostly link their new units to slightly less recent units, meaning that the DAG grows only in one direction.
is not true in high load, the DAG becomes very wide.
Adding to the
bolded part above, every
node will pick its own main chain (witnesses are no special). You are demonstrating the simple fact that under high throughput and wide DAG, different nodes have different views of the world, hence build different MCs, and that the trailing part of the MC is constantly rebuilt as new units arrive. However, the algorithm that they use to build the MC guarantees that the portion of the MC that is older than certain point (stability point) is never rebuilt, it is stable. It is normal that there is no consensus (yet) about the unstable trailing part.
Sorry, didn't bother to read the actual article. Try
https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed:
In its classic interpretation, the CAP theorem ignores latency, although in practice, latency and partitions are deeply related. Operationally, the essence of CAP takes place during a timeout, a period when the program must make a fundamental decision-the partition decision:
cancel the operation and thus decrease availability, or
proceed with the operation and thus risk inconsistency.
Quoting from the whitepaper:
15. Partitioning risk
The network of Byteball nodes can never be partitioned into two parts that would both continue operating without noticing. Even in the event of a global network disruption such as a sub-Atlantic rat cutting the cable that connects Europe and America, at least one of the sides of the split will notice that it has lost the majority of witnesses, meaning that it can’t advance the stability point, and nobody can spend outputs stuck in the unstable part of the MC. Even if someone tries to send a double-spend, it will remain unstable (and therefore unrecognized) until the connection is restored. The other part of the split where the majority of witnesses happens to be, will continue as normal.
In other words, in the minority partition, confirmations will just stop before the connection is restored.