Aller au contenu principal

Resilience Design Pocket Deck

Recall resilience patterns for bounding failure and preserving core user journeys.

reliability-engineering4 min read

Retry vs fallback When should you retry, and when should you fallback? Retries recover brief faults; fallbacks preserve experience when dependency health is uncertain. Objection If the dependency fails, users should just wait because the complete answer is better. A noncritical enrichment service slows a checkout-adjacent page. Your line Completeness is not worth blocking the core journey. Set a short timeout and use a fallback when the enrichment misses its budget. The trap is letting optional correctness consume critical-path reliability. It prioritizes the user outcome over feature perfection. Idempotency What does idempotency protect? Safe replay: the same operation can be…

Read the full lesson

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

← Back to library

Nous contacter