History[07][08][09]

CockroachDB is inspired by Google’s Spanner and F1 to address fault tolerance and distributed consistency.

Concurrency Control[06]

Data Model[06]

Foreign Keys[10]

CockroachDB supports foreign keys.

Indexes[11][12][13]

CockroachDB's indexes are stored in RocksDB's LSM tree implementation.

Isolation Levels[06][14][15]

CockroachDB supports serializable snapshot isolation (SSI). It is implemented using RocksDB snapshot capability.

Joins[16]

CockroachDB supports all standard SQL joins. Distributed joins are performed via a shuffle by hash strategy, or a batched nested loop strategy. Broadcast joins are not supported.

Logging[06]

Query Compilation

Query Execution[17]

CockroachDB supports distributed SQL execution. The gateway query node is responsible for creating a DAG of SQL processors and distributing them across the cluster, like in F1. The individual SQL processors operate in either a tuple-at-a-time mode, which supports all SQL queries in CockroachDB, or a vectorized mode, which supports a subset of SQL, depending on query cardinality.

Query Interface[18]

CockroachDB aims to provide standard SQL with extensions, but some standard SQL functionality is under development.

Storage Architecture[06]

The backend storage in CockroachDB is RocksDB. It is disk-oriented storage.

Storage Model[19]

CockroachDB stores its data in the distributed key-value store.

Storage Organization

Stored Procedures

System Architecture[06]

CockroachDB has two layers, the SQL layer and the storage layer. The SQL layer sits on top of the transactional and strongly-consistent distributed key-value store. In the key-value store, the key ranges are divided and stored in RocksDB and replicated across cluster. It exports structured data API of relational concepts. It exports standard SQL interface at the SQL layer. The SQL layer translates SQL statements into calls to structured data API.

Views