Should a load balancer always move requests away from an unhealthy server?
No. If most destinations share the same failing dependency or overload condition, moving every request can concentrate load and spread the failure. Routing should use health, capacity and failure-domain signals, and switch to admission control or load shedding when no safe destination has headroom.
Answered in
Designing Gateways That Fail Without Taking the Fleet DownA technical blueprint for gateway overload control: N-1 capacity, bounded queues, load shedding, isolated failover and controlled recovery.
Read the full analysisOther questions this article answers
More system design & architecture questions
- How much spare capacity should a gateway keep?
- Why are bounded queues important for availability?
- Can a circuit breaker prevent every cascading failure?
- Why does pagination improve API performance beyond just 'smaller responses'?
- Why is asynchronous logging faster than writing logs synchronously?
- When does caching actually help API performance, and when doesn't it?
- Why does payload compression trade CPU time for network time, and when is that worth it?
- What specific overhead does connection pooling eliminate?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.