advancedResilience Patterns378 of 469
A downstream API is unavailable and your retries generate even more traffic. How do you redesign the retry strategy?
Tests whether you reach for exponential backoff with jitter (to avoid synchronized retry storms) capped by a circuit breaker that stops retrying altogether once failures sustain, instead of fixed-interval retries that pile on load exactly when the dependency is already struggling.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response