This post was originally published on November 3, 2015, the year Cockroach Labs was founded. Eight years and 85,670 GitHub commits later, it’s still absolutely true: Go was the “write stuff” for CockroachDB. The first question many developers ask us is what our experience has been writing a distributed database in Go, a garbage-collected language. JVM garbage collection is notoriously expensive, s

In August, we published a blog post entitled “Why Can’t I Run a 100-Node CockroachDB Cluster?”. The post outlined difficulties we encountered stabilizing CockroachDB. CockroachDB stability (or the lack of) had become significant enough that we designated it a “code yellow” issue, a concept borrowed from Google that means a problem is so pressing that it merits promotion to a primary concern of the

Scale to meet demandDatabase bottlenecks stifle business performance and growth. CockroachDB removes the complexity of manual sharding and scales horizontally as workload volumes increase. SQL that scales horizontallyA distributed system that feels like a single, logical database. Save time by eliminating the need to create and maintain separate database shards. Scale reads, writes, and database c

[As of February 23, 2017, CockroachDB Beta Passed Jespen Testing] We at Cockroach Labs absolutely love Aphyr’s work. We are avid readers of the Jepsen series – which some know as a high quality review of the correctness and consistency claims of modern database systems, but which we really know as “Aphyr’s hunting tales about the highest profile bugs in our industry.” Most of us read each new blog