Load balancing through the years
summary
Starts from a concrete failure: legacy Cisco CSS/ACE boxes choke when SSL daughterboard overload causes opaque behavior and engineering takes 8 months to validate the root cause. Modern systems shift that integer problem into software: F5 Distributed Cloud and its SaaS portal expose per-subsystem metrics, network diagrams and event detail so overloads are visible across thousands of connections, and logs can be forwarded to SIEM/Splunk offload pipelines with AI-assisted alerts to speed diagnosis and remediation.
AI-written summary · about
chapters (5)
related talks
23mBalancing on the Edge: Transport Affinity without Network State
46mKeeping the Balance: Load Balancing Demystified
06mBuilt in the Open: Why Cisco Is Betting on eBPF, Ci...
26mF10: A Fault-Tolerant Engineered Network
30mKeeping the Balance: Internet-Scale Loadbalancing Demystified
32mLive Q+A 2
33mCloud Native Load Balancing From Scratch
32mYour Load Balancer is Your New Perimeter: Attacks & Defenses at Scale