What is a health check and why does it matter?
A periodic probe that tells the balancer whether a backend can take traffic. Without it, a dead server keeps receiving requests. A bad one is just as harmful: a check that only tests the process is up will happily route traffic to a server whose database connection is broken.
Answered in
Load Balancers Demystified: Layer 4 vs Layer 7, Algorithms and Health ChecksWhat a load balancer decides, how Layer 4 and Layer 7 differ, which algorithm fits which traffic, and the health-check mistakes that cause outages.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the architectural difference between an API Gateway and a Reverse Proxy?
- When should an architecture use Layer 4 instead of Layer 7 load balancing?
- How do edge ingress layers prevent backend cascading thundering herds?
- What algorithm is best for sticky sessions without breaking even distribution?
- How can a CDN improve performance for dynamic requests?
- What is the hardest part of operating behind a CDN?
- How can a CDN help with traffic surges or DDoS attacks?
- What is the difference between a Push CDN and a Pull CDN?
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.