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'.
CockroachDB was so named because of its ability to survive failures. In this post, we will cover architectural considerations when building high availability services on top of CockroachDB.
This post covers what Data Subject Rights are and how they can affect GDPR compliance for your company.
A Q&A with CEO Spencer Kimball about what GDPR compliance means for companies and how the process can be made easier using CockroachDB.
Still working on GDPR compliance? CockroachDB might be able to help.
Geo-partitioning keeps user data close to the user, reducing latency and improving UX while archival-partitioning allows you to store data efficiently.