Case studies

Familiar components, each given a single responsibility, carried a very small team a long way.

Retrying with the same key returns the stored outcome instead of charging a second time.

Coalescing identical reads cut database load before the storage engine was ever replaced.

Accepting writes during a partition means the application must reconcile divergent versions later.

The recovery paths that were assumed to exist had never been exercised until the night they were needed.