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.
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.
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.
The 2022 Cloud Report is the only cloud performance report to compare AWS, Azure, and GCP on benchmarks that reflect critical applications and workloads.
Today we’re introducing Pebble, a RocksDB-inspired and RocksDB compatible key-value store written in Go that brings greater stability to CockroachDB.
Now in its third year, the 2021 Cloud Report from Cockroach Labs compares AWS, Azure, and Google (GCP) to tell realistic performance stories on behalf of mission-critical OLTP applications.
The 2020 Cloud Report compares AWS, GCP, and Azure on microbenchmarks and customer-like-workloads to understand performance tradeoffs within each cloud.
CockroachDB serverless is the first truly scalable serverless SQL database. Learn how it works and how a serverless sql database can relieve the operational burden of developers.
Key learnings about how to get the best performance from GCP, AWS, and Azure based on original research and conversations with the big three.
Customers rely on us to help navigate the increasingly competitive cloud wars. This inspired the 2018 Cloud Report, a benchmark of AWS and GCP on performance, latency, CPU, network, I/O, and cost.
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.
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.
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.
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.
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.
We’re pleased to announce the availability of Managed CockroachDB, the fully hosted and fully managed service run by Cockroach Labs that makes deploying, scaling, and managing effortless.
One of the headline features of CockroachDB is its full support for ACID transactions across a distributed database. In this post, we’ll explain...
If someone knows even a little about Spanner, the first question they have is: "How does CockroachDB provide external consistency without atomic clocks?"
CockroachDB 19.2 improves latency, reliability, and usability. We’re bringing the speed of distributed transactions closer to the theoretical minimum.
This blog post outlines how CockroachDB executes queries and shares Cockroach Labs' vision for future work on distributed processing.
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.
To protect concurrent transactions from anomalies that can break the consistency of CockroachDB, we require an Isolation guarantee...
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.
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.
CockroachDB's consistency model fits somewhere between serializability and linerarizability. We're proposing a new marketing phrase for CRDB's guarantees: no stale reads.