🔒 Paid

Dependency Rate-Limit Exhaustion

The Aggregation Service calls a third-party provider that enforces a hard request quota on a rolling 10-minute window — once the quota is gone for that window, every call fails until it resets. The provider relationship is commercial and the quota cannot be raised mid-incident. Multiple product surfaces depend on this call path, and one of them is an optional enrichment feature rather than a core one. Bring the dependency's call volume to a level the remaining quota can sustain for the rest of the window, without assuming that retrying a failed call is free.

Difficulty
Senior
Expected Time
~15 min
Category
Microservices & Dependencies

Skills

  • Recognizing that retries against a hard quota consume the same budget as original requests
  • Reducing sustained call volume durably versus suppressing a feature
  • Evaluating request coalescing and caching as quota-preserving strategies
  • Prioritizing traffic under a shared, shrinking resource constraint

System Architecture

  • Clients
  • API
  • Aggregation Service
  • Third-Party Dependency

This is a Pro scenario. Upgrade to Pro to unlock it.

Upgrade to ProBack to Incidents