1
CockroachDB 2.0 Performance Makes Significant Strides
Learn which performance metrics matter, why to demand benchmark TPC-C results under serializable isolation, and how CockroachDB 2.0’s performance compares to 1.1.
Cockroach Labs Blog
Cockroach Labs develops CockroachDB and Cockroach Continuum, an agentic database cloud-native, distributed SQL database designed for extreme resilience, seamless horizontal scaling, and global deployment.
- Popular posts
- 53
- Total points
- 11,051
- HN comments
- 4,787
- Rank
- #83 company
Visit cockroachlabs.com → On Hacker News Jun 2015 – Oct 2026
Databases & Data 33Software Engineering 27Systems & Performance 15Tech Industry & Business 11Programming Languages 3Infrastructure & DevOps 3
2
A Brief History of High Availability
The perennial question of homo sapiens is, 'How did we get here?' Today we're going to take a crack at answering that: where 'here' is defined as 'high availability for web services'.
3
Raft Is So Fetch: The Raft Consensus Algorithm Explained Through Mean Girls
Understanding the Raft Consensus Algorithm can be tough. In honor of "Mean Girls" day (October 3), we present Raft as explained through the movie "Mean Girls."
4
Distributed Databases Should Work More Like CDNs
Distributed database performance––both latency and uptime––can be dramatically improved with CDN-like multi-region deployments.
5
CockroachDB Stability Post-Mortem: From 1 Node to 100 Nodes
In August, we wrote about our concerted stability effort. Today, we've more than achieved our CockroachDB stability goal of running a 100-node cluster.
6
Parallel Commits: A New Atomic Commit Protocol for Distributed Transactions
Parallel Commits are an atomic commit protocol in CockroachDB. The feature promises to halve the latency of distributed transactions by performing all consensus round trips required to commit a transaction concurrently.
7
The Limits of the CAP Theorem
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.
8
Building CockroachDB on top of RocksDB
CockroachDB uses RocksDB for its storage engine because of RocksDB's rich feature set, which is necessary for a complex product like a distributed SQL database.
9
How CockroachDB Does Distributed, Atomic Transactions
One of the headline features of CockroachDB is its full support for ACID transactions across a distributed database. In this post, we’ll explain...
10
Living Without Atomic Clocks
If someone knows even a little about Spanner, the first question they have is: "How does CockroachDB provide external consistency without atomic clocks?"
11
Antithesis of a One-in-a-Million Bug: Taming Demonic Nondeterminism
With the help of Antithesis, a startup from the founders of FoundationDB, CockroachDB engineers were able to track down and reproduce a most elusive one-in-a-million bug, nearly deterministically!
12
Local and distributed query processing in CockroachDB
This blog post outlines how CockroachDB executes queries and shares Cockroach Labs' vision for future work on distributed processing.
13
Serializable, Lockless, Distributed: Isolation in CockroachDB
To protect concurrent transactions from anomalies that can break the consistency of CockroachDB, we require an Isolation guarantee...
14
CockroachDB's Consistency Model
CockroachDB's consistency model fits somewhere between serializability and linerarizability. We're proposing a new marketing phrase for CRDB's guarantees: no stale reads.
15
Progress in performance and scalability with CockroachDB
CockroachDB 2.1 is 50x more scalable than Amazon Aurora at less than 2% of the price per tpmC. Read on to see performance benchmarks of CockroachDB 2.1, including the latest TPC-C results.