Reliability Pattern Cards

What should be named before choosing a pattern? The user-visible promise, the owning boundary, and the failure behavior that would break trust. This prevents pattern-first architecture. Retry versus idempotency: which problem does each solve? Retries are safer when receivers are idempotent. “Just cache it so it is faster.” A slow query appears in a design review. Your line Let’s first name how stale this value may be, who sees it, and how invalidation works; then we can decide whether a cache is the right trade-off. Speed pressure can hide correctness risk. It preserves the latency goal while forcing the team…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in