If someone knows even a little about Spanner, the first question they have is: "How does CockroachDB provide external consistency without atomic clocks?"
I experimented with implementing the Redis protocol on top of CockroachDB, scratching the itch on the question: Could CockroachDB ever replace Redis?
I periodically need to make changes to tables… mostly adding columns. Very simple with the alter table command… But my tables have up to 40 million rows now and they are growing fast… So those alter table commands take several hours… Since I’m using amazon RDS [sic], I can’t have slave servers to play with and then promote to master. So my question is if there’s a way to do this with minimal downtime?
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.
The first question many developers ask us is what our experience has been writing a distributed database in Go, a garbage-collected language.
SQL? I thought CockroachDB was a key-value store?!? In the past we described CockroachDB as a distributed, transactionally consistent, key-value store.
One of the headline features of CockroachDB is its full support for ACID transactions across a distributed database. In this post, we’ll explain...
In CockroachDB, we use the Raft consensus algorithm to ensure that your data remains consistent even when machines fail.