CockroachDB 1.1 includes support for faster migrations from legacy databases, simplified cluster management, and improved performance.
Cockroach Labs was at Hack the North 2017 for the second year where the team met some fantastic teams working with CockroachDB.
This post is the first in a series on how CockroachDB handles its data and discusses the mechanisms it uses to rebalance and repair.
Using CockroachDB means shifting operational thinking from disaster recovery to disaster resilience, and completely side steps the risks associated with vendor lock-in.
CockroachDB makes it easier to manage and scale mission-critical data, and DC/OS provides elastic scale, zero downtime, and hassle-free operations.
Most databases treat strong transaction isolation as exotic, expecting applications to work with faster but unsafe isolation modes that can expose them to subtle bugs. CockroachDB provides SERIALIZABLE transactions by default, ensuring you always see the consistency you expect.
By redefining the hiring process using exercise based interviews and removing resumes, we create a fairer process that leads to better hiring decisions.
The interviews at Cockroach Labs are exercise-based, focused on practical, day-in-the-life style work tasks without the bias of resumes.
How we implemented consistent, distributed, incremental backup in CockroachDB.