Multiple ChoiceHard 45s
Bulkhead isolation
A shared thread pool serves both a slow external payment API and fast internal calls. One day payments hang and everything stalls. Which pattern prevents this?
Options
- 1Retry with jitter: add randomized delays between attempts so retries do not synchronize into a storm
- 2Horizontal autoscaling only: add more service instances automatically when the slow payment calls pile up
- 3Adding a CDN in front: cache the payment API responses at the edge to absorb and offload the heavy load
- 4Bulkhead: isolate thread/connection pools per dependency so one slow dependency cannot exhaust resources for others
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.