Add a Timeout Before You Add Retries
Design a mesh timeout and retry policy that respects the caller latency budget.
cart-api needs discounts-api results, but mobile checkout must respond within 2 seconds. Latency-budget policy: caller budget -> route timeout -> bounded retry -> fallback behavior. Adding retries first feels resilient, but it can spend the entire user latency budget and add load during partial failure. Before cart-api waits up to 8 seconds and retries twice. Users see long spinners, and discounts-api gets extra traffic while degraded. After cart-api uses a 900 ms timeout, one retry for safe transient failures, and a clear fallback if discounts-api misses the budget. Name caller budget Mobile checkout has 2 seconds total. Reserve 700 ms…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in