Home · Tech in 60 Seconds

Transcript

1. Traffic just went 10x. What do you put in front of your servers?
2. A load balancer. Think of the greeter at a bank. It has three jobs.
3. One: split the load. Desk one, desk two, desk three, in turn. The default: round robin.
4. Two: skip the sick desk. By default, it checks every 30 seconds. Fail twice, you're out.
5. Three: stick the regulars. A cookie notes their desk, so the cart stays put.
6. Nice. And if the load balancer itself goes down?
7. Redundancy. The main one pings every second. If that stops, the backup takes over.
8. L4 sees only address and port. L7 reads the request, so checkout goes to checkout servers.
9. Three words: split, skip, stick.
10. Split is round robin, skip is health checks, stick is sticky sessions.
11. Practical tip: say it in numbers, like "30 seconds, two misses." Numbers make you more convincing.

Sources

1. AWS, "What is an Application Load Balancer?" (Elastic Load Balancing 문서, 2026-10-26 확인)
2. AWS, "Edit target group attributes for your Application Load Balancer" (Routing algorithm · Sticky sessions, 2026-10-26 확인)
3. AWS, "Health checks for Application Load Balancer target groups" (2026-10-26 확인)
4. HAProxy, "architecture.txt" (HAProxy 1.3 문서, `cookie SERVERID insert indirect` 예 — 쿠키 "SERVERID=A" 로 같은 서버에 보냄, 2026-10-26 확인)
5. IETF, RFC 5798 "Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6" (2010-03)
6. AWS, "What is a Network Load Balancer?" (2026-10-26 확인)
7. Microsoft Learn, "What is Azure Load Balancer?" (2026-07-07)
8. Microsoft Learn, "What is Azure Application Gateway" (2026-09-10, OSI 7계층·URL 경로·호스트 헤더 라우팅·쿠키 기반 세션 고정)