#engineering

Part two of the distributed cache series — implementing consistent hashing and proving, with a test, that a node can leave without losing data.

The first part of a series on building a distributed cache from scratch — starting with the design decisions that everything else depends on.

Clever code feels great to write and terrible to maintain. Here's what changed my mind, and the three questions I ask before landing anything tricky.