The load balancer steers flood from ads, bots or peak traffic on your announced domain to the least-loaded idle node IP.
The balancer constantly tests whether Web A, B and C return HTTP 200. A dead node never receives customers — traffic goes to a healthy one (Web-B).
If a TV ad or botnet spike hits, the stack stays up by adding machines in seconds (expanded infrastructure / auto-scale).
Encrypted visitor traffic must be decrypted on the origin and that exhausts the web service. The load balancer terminates TLS and eases backend nodes by about 30%.
No. A single origin can fail, but our Layer 4 load balancers run high-availability pairs. If one unit is unplugged, another is already live.
Round robin (A -> B -> C), least connection (send to the node with fewest open connections) and IP hash (visitor A always hits machine A), plus other flexible rules.