Applications built on a traditional failover pattern with two data centers (and no access to a third on-prem or cloud region) used to face challenges in ensuring high resilience with CRDB. New in v23.2, physical cluster replication functionality now allows limited distribution applications to survive full cluster failures — with RPO and RTO measured in seconds rather than minutes.

CockroachDB offers insights into distributed database technology, scalable SQL architecture, and cloud-native data management, providing documentation, tutorials, and case studies for building resilient and highly available applications. By exploring CockroachDB's curated content, developers and database administrators can learn about distributed SQL databases, multi-region replication, and transactional consistency for powering mission-critical services in the cloud. Whether you're migrating from legacy databases, scaling globally distributed applications, or ensuring data resilience in the face of failures, CockroachDB offers resources to meet your data storage and processing needs.

CockroachDB

CockroachDB offers physical cluster replication, an asynchronous and consistent way to keep two clusters up to date with zero RPO and near-zero RTO. The replication process provides granular observability and control over data replication and allows for a defense-in-depth approach. Physical cluster replication offers significantly lower RPO and RTO compared to traditional backup and restore methods.

Prevention > Recovery: Physical cluster replication

What is physical cluster replication and how does it work?

When would you use physical cluster replication?

Why is physical cluster replication important?

Watch physical cluster replication in action