Recap: Design Heuristics

Fifteen pairs grouped by the pressure that starts them, and the rule for a conflict.

A heuristic maps a pressure to a pattern as a first guess, to be checked against the numbers (Matching a Pressure to a Pattern).
Distance and reads point to the edge and the cache (Heuristics Example: A Global News Site).
Writes, failures and retries point to queues, limits and idempotency keys (Heuristics Example: A Flash Sale Checkout).
When two heuristics conflict over the same data, a named requirement decides, and both are adjusted to meet it (Heuristics That Pull Against Each Other).
Failures at scale show as symptoms, and each has a name and a fix (Practice: Diagnosing Ten Failures at Scale).
A first design runs from requirements to estimates to parts, each tied to its pressure (Practice: A First Design for a Chat Application).

← → move through sections and cards