Why are Go executable programs larger than expected? We visualized the CockroachDB binaries using tree maps to find out.
The decision to make CockroachDB and PostgreSQL compatible was driven by a desire to be accessible to an ecosystem of drivers, existing code, and developer knowledge.
This blog post outlines how CockroachDB executes queries and shares Cockroach Labs' vision for future work on distributed processing.
In this post we share performance and functionality progress that has been made on SQL joins in CockroachDB and what to expect in CockroachDB 1.0.
In this post, we provide details on how CockroachDB uses system memory on each node, and what you can do to keep memory usage in CockroachDB under control.
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.
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.
This blog post explains how to run CockroachDB in a FreeBSD jail. This is lighter weight and as secure as running Docker on FreeBSD.
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.
We at Cockroach Labs absolutely love Aphyr's work. We are avid readers of the Jepsen series – which some know as high quality reviews of correctness...