Load Balancing Building Blocks
Talkat SREcon19 Europe/Middle East/Africa · on Thursday, 2019-10-03· at 11:00· Track 1: The Liffey B·
summary
Facebook runs a seven-layered chain of load balancers per request (DNS → POPs → L4 → L7 → backends) and uses DNS steering plus a tool called cartographer to spill over capacity across regions. DNS TTLs are misleading (1 minute TTL yields ~50% sticky traffic after 10 minutes). POPs cut round-trip setup from ~450ms to ~90ms even for dynamic requests by keeping long-lived connections. Global L4 aggregation uses maglev hashing with converged health checks and direct responses; the open source implementation is catran and it operates at Facebook scale.
AI-written summary · about
chapters (7)
- 0:00Introduction to load balancing
- 3:46Layer 4 and 7 balancers
- 8:08DNS load balancing
- 14:59Points of presence (POPs)
- 19:44Global traffic management
- 22:31Maglev and software load balancing
- 33:39System integration and Q&A
related talks
44mDNS at Facebook
44mDNS at Facebook
38mFacebook's Data Center Fabric
46mKeeping the Balance: Load Balancing Demystified
30mKeeping the Balance: Internet-Scale Loadbalancing Demystified
51mHow to Serve a Billion Users and Deliver Terabits of Traffic
19mEngineering Facebook's Data Center Network: Challenges and Limitations
04mLoad balancing through the years
