The perennial question of homo sapiens is, 'How did we get here?' Today we're going to take a crack at answering that: where 'here' is defined as 'high availability for web services'.
CockroachDB was so named because of its ability to survive failures. In this post, we will cover architectural considerations when building high availability services on top of CockroachDB.
This post explains how CAP-Consistent systems can be highly available, how the CAP theorem applies to CockroachDB, and why consistency is the better choice.