systemsWritten by Arjun Narayan and Peter MattisArjun Narayan and Peter Mattis on January 17, 2019
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.
systemsWritten by Nathan VanBenschotenNathan VanBenschoten on January 10, 2019
This post introduces Transactional Pipelining which dramatically speeds up distributed transactions with respect to the latency cost of distributed consensus.
applicationsWritten by Alex RobinsonAlex Robinson on December 20, 2018
This blog covers the practical experience of running a distributed system across multiple Kubernetes clusters including what makes it challenging and what solutions are available (some of which we run in production).
systemsWritten by Andy KimballAndy Kimball on November 8, 2018
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.
applicationsWritten by Matt JibsonMatt Jibson on September 27, 2018
sqlfmt is an opinionated SQL formatter. It’s not designed to be completely customizable, and we hope to remove options over time. Use it and stop thinking about how to format SQL.
systemsWritten by Sean LoiselleSean Loiselle on August 23, 2018
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.