How do you ensure that the log messages contain enough information to be useful without encumbering the development of new code?
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.
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.
Cgo is an important part of Go: It's your window to calling anything that anything that has C bindings. But while cgo works for us, it hasn’t come for free.
In this post, we’ll share a few powerful optimizations that mitigate many of the performance problems common to Go garbage collection.
The first question many developers ask us is what our experience has been writing a distributed database in Go, a garbage-collected language.