Compliance with data localization laws is difficult and expensive. It’s particularly expensive with a monolithic DB. This blog outlines the yellow brick road towards compliance and flexibility for shifts in the data protection tectonic plates.
Cockroach CEO Spencer Kimball reads the tea leaves on the evolution of data protection laws, and what companies can do to prepare for the unknown.
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.
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.
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.
This post introduces Transactional Pipelining which dramatically speeds up distributed transactions with respect to the latency cost of distributed consensus.
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.
Joins are one of the most powerful features relational databases offer––but optimal executions are NP-hard to find. How do you support them in an OLTP database?
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'.