Overview

CockroachDB is a cloud-native, fully-managed, distributed SQL database that has been architected and built from the ground up to scale easily and survive any failure. It delivers a familiar SQL interface and automates scale for both reads and writes without operational overhead. It is a database built for transactional workloads and guarantees data consistency for workloads in a single region or even globally distributed environments. CockroachDB is the only database architected to deliver on the core distributed principles of atomicity, scale and survival so you can manage your database IN Kubernetes. Using StatefulSets, CockroachDB is a natural for deployment within a Kubernetes cluster. CockroachDB can also be deployed on VM's created/managed via Red Hat OpenShift Virtualization.

GLOBAL SCALE: Simplify global deployments: Scale your database by simply adding new nodes and avoid any manual manipulation of data. CockroachDB automatically rebalances and replicates data throughout the cluster. Automatic and continuous rebalancing of data between nodes eliminates the pain of manual sharding. Progress can be made as long as a majority of nodes is available, preventing RTO if a node goes down. CockroachDB distributes data to avoid failure domains and help address heavy workloads.
GUARANTEED CONSISTENCY: Right data all the time: In a distributed environment, competing transactions can come from anywhere. Only CockroachDB provides the highest level of isolation (serializable) in a distributed database. Maintain ACID compliance while enjoying the benefits of a distributed system. Run critical workloads like inventory management and IAM in a distributed setting. Trust all copies of your data are up-to-date with synchronous writes across nodes; if one node fails, no data is lost. Cutting edge distributed systems ensure your data is not only correct, but also available. Every node can service writes so you can scale from local to regional deployments and still guarantee data correctness.
ULTRA-RESILIENT: Survive any failure, even a full region: CockroachDB delivers an always-on and available database designed so that any loss of nodes is consumed without impact on availability. It creates & manages replicas of your data to ensure reliability. Upgrade to new versions of CockroachDB without interrupting a cluster’s overall health and operations. Back up your full cluster to services like AWS S3, Google Cloud Storage, or NFS for the unlikely case you need to restore data. Roll back CockroachDB to the exact moment before a mistyped delete or update happened. CockroachDB is an active-active database that can reduce RPO to zero.
MULTI-REGION: Serve customers everywhere: CockroachDB is the only database in the world that enables you to attach ‘location’ to your data at the row level. This capability allows you to regulate the distance between your users & their data. Define your read/write latency requirements for tables with simple SQL commands, and CockroachDB distributes data under the covers. With just a few SQL statements, define survival goals for your databases so they handle AZ or region loss without impact to performance. Simply deploy your app to multiple regions without the need for rearchitecting or complex logic to determine where data lives.

Next steps

Get started with OpenShift

A container platform to build, modernize, and deploy applications at scale.

Try it

Deployment options

Resources

Cockroach University Enroll in our free course, covering distributed databases & cloud-native applications
Cockroach University - Getting Started Learn the practical first steps to CockroachDB
CockroachDB FAQ's Overview and best practices of CockroachDB
Quick Start Guide Get up and running quickly with our Quick Start Guide
Configuration Guide View details about how to configure for your environment and needs
Troubleshooting Guide Experiencing problems? Check this guide first to solve common issues

Certifications

Learn about Red Hat Certification and Partner Validation

Red Hat certified products are tested to meet Red Hat’s criteria and supported as defined in the Red Hat Collaborative Support Process.

Partner validated products are tested by Red Hat Partners and supported as defined in the Red Hat Third Party Component Policy.

Certification standards

Runs on OpenShift
Fully containerized
Continuous vulnerability scans
Collaborative support
Meets best practicesThe certified software follows Red Hat’s best practices for deployment on Red Hat OpenShift clusters.

Certified components

Deploy & use

Quick start and configuration

Getting started

FAQs

What is CockroachDB?

CockroachDB is a distributed SQL database built on a transactional and strongly-consistent key-value store. It scales horizontally; survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports strongly-consistent ACID transactions; and provides a familiar SQL API for structuring, manipulating, and querying data. CockroachDB is inspired by Google's Spanner and F1 technologies, and the source code is freely available.

When is CockroachDB a good choice?

--- CockroachDB is well suited for applications that require reliable, available, and correct data, and millisecond response times, regardless of scale. It is built to automatically replicate, rebalance, and recover with minimal configuration and operational overhead. Specific use cases include: Distributed or replicated OLTP Multi-datacenter deployments Multi-region deployments Cloud migrations Cloud-native infrastructure initiatives CockroachDB returns single-row reads in 2ms or less and single-row writes in 4ms or less, and supports a variety of SQL and operational tuning practices for optimizing query performance. However, CockroachDB is not yet suitable for heavy analytics / OLAP.

How does CockroachDB scale?

CockroachDB scales horizontally with minimal operator overhead. You can run it on your local computer, a single server, a corporate development cluster, or a private or public cloud. Adding capacity is as easy as pointing a new node at the running cluster. At the key-value level, CockroachDB starts off with a single, empty range. As you put data in, this single range eventually reaches a threshold size (64MB by default). When that happens, the data splits into two ranges, each covering a contiguous segment of the entire key-value space. This process continues indefinitely; as new data flows in, existing ranges continue to split into new ranges, aiming to keep a relatively small and consistent range size. When your cluster spans multiple nodes (physical machines, virtual machines, or containers), newly split ranges are automatically rebalanced to nodes with more capacity. CockroachDB communicates opportunities for rebalancing using a peer-to-peer gossip protocol by which nodes exchange network addresses, store capacity, and other information.

How does CockroachDB survive failures?

CockroachDB is designed to survive software and hardware failures, from server restarts to datacenter outages. This is accomplished without confusing artifacts typical of other distributed systems (e.g., stale reads) using strongly-consistent replication as well as automated repair after failures. Replication CockroachDB replicates your data for availability and guarantees consistency between replicas using the Raft consensus algorithm, a popular alternative to Paxos. You can define the location of replicas in various ways, depending on the types of failures you want to secure against and your network topology. You can locate replicas on: Different servers within a rack to tolerate server failures Different servers on different racks within a datacenter to tolerate rack power/network failures Different servers in different datacenters to tolerate large scale network or power outages In a CockroachDB cluster spread across multiple geographic regions, the round-trip latency between regions will have a direct effect on your database's performance. In such cases, it is important to think about the latency requirements of each table and then use the appropriate data topologies to locate data for optimal performance and resiliency. For a step-by-step demonstration, see Low Latency Multi-Region Deployment. Automated Repair For short-term failures, such as a server restart, CockroachDB uses Raft to continue seamlessly as long as a majority of replicas remain available. Raft makes sure that a new “leader” for each group of replicas is elected if the former leader fails, so that transactions can continue and affected replicas can rejoin their group once they’re back online. For longer-term failures, such as a server/rack going down for an extended period of time or a datacenter outage, CockroachDB automatically rebalances replicas from the missing nodes, using the unaffected replicas as sources.

Certifications

Learn about Red Hat Certification and Partner Validation

Certification standards

Runs on OpenShift
Fully containerized
Continuous vulnerability scans
Collaborative support
Meets best practicesThe certified software follows Red Hat’s best practices for deployment on Red Hat OpenShift clusters.

Quick start and configuration

Getting started

CockroachDB Certified

Next steps

Get started with OpenShift

Certifications

Certified components

Quick start and configuration

Get started

Platforms

Products & services

Try, buy, sell

Help

About Red Hat Ecosystem Catalog

Red Hat legal and privacy links

Red Hat legal and privacy links

CockroachDB Certified

Next steps

Get started with OpenShift

Certifications

Certified components

Quick start and configuration

Get started

Install operator from OperatorHub using

Deployment methods

CockroachDB-operator-bundle-marketplace

CockroachDB-operator-bundle