CockroachDB 1.0
Launching CockroachDB 1.0, a production-ready release with distributed SQL and multi-active availability in two tiers: CockroachDB Core and CockroachDB Self-hosted.
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.
Visit cockroachlabs.com → On Hacker News Jun 2015 – Oct 2026
Databases & Data 33Software Engineering 27Systems & Performance 15Tech Industry & Business 11Programming Languages 3Infrastructure & DevOps 3
Launching CockroachDB 1.0, a production-ready release with distributed SQL and multi-active availability in two tiers: CockroachDB Core and CockroachDB Self-hosted.
Golang executable files get too large for reasons that are not relevant to server software with long-running processes, like CockroachDB, and its incurred space cost is particularly inconvenient for large, feature-rich programs.
We started Cockroach Labs with a clear objective: build the database we'd been itching after for years, and build it as open source, from the start. Today, we’re launching CockroachDB for everyone.
Since our 1.0 release, we have been hard at work making CockroachDB 2.0 the database that enables a company’s data layer to evolve with their business -- whether they are in a single datacenter or expanding around the world.
Today we’re introducing Pebble, a RocksDB-inspired and RocksDB compatible key-value store written in Go that brings greater stability to CockroachDB.
The original draft of the analysis we presented was reviewed internally, and yet still inaccuracies slipped through. We are a team of humans. We make mistakes. We take full responsibility for the invalid conclusions we published.
How Cockroach Labs built MOLT Sinai, an AI coding “teaching hospital” that shipped IBM Db2 migration support in under two days.
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."
Using vectorized processing in an execution engine makes more efficient use of modern CPUs by changing the data orientation (from rows to columns) to get more out of the CPU cache and deep instruction pipelines by operating on batches of data at a time.
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.
CockroachDB 2.1 includes a brand-new, built-from-scratch, cost-based SQL optimizer. This post explains what a cost-based SQL optimizer is, and tells the story of how we decided we really, really needed one.
CockroachDB 1.1 includes support for faster migrations from legacy databases, simplified cluster management, and improved performance.
CockroachDB is PostgreSQL compatible in order to be accessible to an ecosystem of drivers, existing code, and developer knowledge.
Support for spatial data and geospatial indexing is one of the most requested features in the history of CockroachDB.
CockroachDB 19.2 improves latency, reliability, and usability. We’re bringing the speed of distributed transactions closer to the theoretical minimum.
Managing state in Kubernetes is difficult because the system’s dynamism is too chaotic for most databases to handle; especially SQL databases that offer strong consistency.
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!
Under READ COMMITTED isolation, PostgreSQL can sometimes miss rows when performing UPDATE, DELETE, SELECT FOR UPDATE, or SELECT FOR SHARE statements. This is due to the EvalPlanQual recheck PostgreSQL adds to these statements to prevent lost-update anomalies.
We have added a new feature: time-travel queries. To our knowledge, we are the first database to have implemented the them.
An interactive demo (using D3) of CockroachDB. Watch as CockroachDB evolves with your application, from proof-of-concept, to multi-node cluster, to international deployment.
We want to give you a database that allows you to quickly and simply build and manage data-intensive applications in the cloud—without worrying about the performance, scale or resilience of those apps. To support that mission, our latest release includes updates that let you build fast and build to last.
One small step for Cockroach Labs, one giant leap for our release numbering.
We introduced Cockroach Labs last June with a simple yet ambitious mission: Make Data Easy. We are now thrilled to launch CockroachDB beta.
How we built a 40x faster hash joiner using vectorized execution.
How we implemented consistent, distributed, incremental backup in CockroachDB.
What do nested transactions look like in an ACID environment? We explore the journey of a nested SQL transaction in CockroachDB in this post.
Cgo is an important part of Go: It's your window to calling anything that anything that has C bindings. But while cgo works for us, it hasn’t come for free.