Multi-region deployment is one of CockroachDB’s most important capabilities. A good design starts with localities, regions and zones, then connects those choices to application latency and resilience requirements.
Localities and survival goals
Administrators define where nodes run and choose survival goals that determine the failures the database is designed to tolerate.
Table locality
REGIONAL BY ROW, REGIONAL BY TABLE and GLOBAL table patterns give different trade-offs between locality, availability and latency.
Operational focus
Production design should also consider network latency, data placement, failover expectations and how changes will be monitored.