Our approach to building CockroachDB has been to focus on correctness, then performance, then stability. Without stability, we don’t have a working database
This blog post outlines how fuzz testing uncovered a Schrodinbug in CockroachDB, how Go was partly to blame, and how we addressed it using strong typing.
It’s with great excitement that we announce the CockroachDB Community Forum, a place to find answers, ask questions, and help out fellow CockroachDB users.
The good news is that CockroachDB’s JOIN seems to work, as in, “it returns correct results.” However, this is just our first, unoptimimized implementation.
If we abandoned our earthly constraints, how could we improve consensus algorithms? Specifically, what would it take to make them faster?
This blog post explains how to run CockroachDB in a FreeBSD jail. This is lighter weight and as secure as running Docker on FreeBSD.
We have added a new feature: time-travel queries. To our knowledge, we are the first database to have implemented the them.
Writing good tests is tricky when the system has a lot of moving parts. In this post we will go over how to outsmart Go dependencies in testing.
Adopting SQL had an unexpected consequence; it forced us to dabble in language design. In this post, we detail our approach to SQL typing in CockroachDB.
CockroachDB's support for SQL means access to a variety of data frameworks and tools. Today, we'll build a simple application in Python using SQLAlchemy...