As we prepare for CockroachDB 1.0, we hired Jepsen author Kyle Kingsbury to run CockroachDB through the Jepsen gauntlet.
Does CockroachDB really survive? When data is written, will a failure really not end up in data loss? Let's explore how CockroachDB checks replication.
To protect concurrent transactions from anomalies that can break the consistency of CockroachDB, we require an Isolation guarantee...
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...
We introduced Cockroach Labs last June with a simple yet ambitious mission: Make Data Easy. We are now thrilled to launch CockroachDB beta.
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?
In CockroachDB, we use the Raft consensus algorithm to ensure that your data remains consistent even when machines fail.
Today, we’re launching CockroachDB for everyone. Use it. Build on it. Contribute to it!