When IT experts consider high availability infrastructure for mission-critical services, their minds often leap to Oracle as the preeminent service provider. But Oracle's database was designed in a pre-cloud world. As a cloud native database, CockroachDB introduces a new way of providing always-on availability, strong data consistency, and distributed performance.
CockroachDB's Consistency Model fits somewhere between serializability and linerarizability. We're proposing a new marketing phrase for CRDB's guarantees: no stale reads.
For DBA teams, minimizing cost and maximizing quality means defining and meeting recovery point objectives (demand zero RPO) and recovery time objectives (RTO).
How we implemented consistent, distributed, incremental backup in CockroachDB.
This post explains how CAP-Consistent systems can be highly available, how the CAP theorem applies to CockroachDB, and why consistency is the better choice.
As we prepare for CockroachDB 1.0, we hired Jepsen author Kyle Kingsbury to run CockroachDB through the Jepsen gauntlet.
Does CockroachDB really survive? When data is written, will a failure really not end up in data loss? Let's explore how CockroachDB checks replication.
To protect concurrent transactions from anomalies that can break the consistency of CockroachDB, we require an Isolation guarantee...
We at Cockroach Labs absolutely love Aphyr's work. We are avid readers of the Jepsen series – which some know as high quality reviews of correctness...
We introduced Cockroach Labs last June with a simple yet ambitious mission: Make Data Easy. We are now thrilled to launch CockroachDB beta.