Pick a corner of the triangle and own it.
Tradeoff Frameworks: pick a corner of the triangle and own it
frame the problem before drawing the system
Lower latency and higher throughput, paid in staleness and ops.
Most design decisions are not 'right vs wrong' but 'which corner of which triangle'. The classic axes — consistency vs availability, latency vs throughput, cost vs reliability, simple vs flexible — recur across every design and every layer.
CAP for the data layer: under partition you must pick consistency or availability. PACELC adds: even when there is no partition, you trade latency vs consistency.
Latency vs throughput at every queue. A bigger batch raises throughput but adds wait. A smaller batch keeps latency low but underutilizes resources. Little's Law makes this exact: L = λW.
Cost vs reliability is geometric. Each extra '9' often roughly multiplies infrastructure cost. 99.9% may cost 1×, 99.99% 2–3×, 99.999% 5–10×.
When a teammate claims 'no tradeoff', look harder — they're usually paying it somewhere else (cost, complexity, future flexibility).
Caching the user-profile lookup.