A downstream service is flaky and increases tail latency. What resilience patterns will you apply on the caller?

Problem Statement

Explanation

Add timeouts and retries with jitter to avoid long hangs. Use a circuit breaker to fail fast after consecutive errors and probe recovery through half-open trials. Provide fallbacks where possible, such as cached data or degraded responses. Expose metrics on error rates and breaker state so on-call teams can tune thresholds.

Code Solution

SolutionRead Only

timeout=300ms; retries=2; circuit=open after 5 failures/30s

Practice Sets

This question appears in the following practice sets:

Monolith vs Microservices

Next Question

Master Interviews
Anywhere, Anytime

A downstream service is flaky and increases tail latency. What resilience patterns will you apply on the caller?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews Anywhere, Anytime

A downstream service is flaky and increases tail latency. What resilience patterns will you apply on the caller?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews
Anywhere, Anytime