Skip to main content

Why use a Self Service Multi-Region instance of CockroachDB

Typically, most applications have some sort of high availability requirements in production. And surviving the failure of a database instance typically means an active/passive setup with asynchronous comms between two instances in two regions. While this works, it is flawed. Using a distributed, active/active database across multiple regions can eliminate downtime and survive nearly any disaster. It can help drive RPO/RTO to near zero. Further, using geo-partitioning, we can place data close to users to drive down query performance across broad geographic distances. And recently, we’ve greatly simplified these features in CockroachDB and brought them to our cloud service. In this session, we are joined by Product Manager Emily Horing to discuss how we made this simple and how to get started. We cover: Getting started with a CockrochDB dedicated instance How to spin up a multi-region instance of CockroachDB How to set up your database to survive region failures How to upgrade and scale a cloud instance of CockroachDB #CockroachDB #DistributedSQL #DistributedSystems