The Limits of Virtualization
Think of standard AWS networking like a highway system: well-engineered, handles millions of cars, and works great for almost everyone. But if you are running a Formula 1 race, you need a private track — no traffic lights, no speed limits, no shared lanes. That is what this topic is about.
For 95% of workloads, standard VPC networking (Internet Gateway, NAT Gateway, VPN) is the right choice. But for the top 5% — High Frequency Trading (HFT), large-scale Machine Learning (ML) training, or regulated banking infrastructure — the software abstractions that make cloud networking convenient become measurable bottlenecks. Every virtualization layer adds latency. Every kernel context switch burns CPU cycles. Every shared internet path introduces jitter.
This topic covers three technologies that operate at or near the physical layer of AWS networking, each solving a distinct class of problem:
- Direct Connect (DX): Replacing the public internet with a dedicated physical fiber-optic cable between your data center and AWS.
- Gateway Load Balancer (GWLB): Inserting a fleet of third-party security appliances (firewalls, intrusion detection systems) into the traffic path transparently — without breaking packet metadata like source IP.
- Elastic Fabric Adapter (EFA): Bypassing the Operating System (OS) kernel entirely so that applications can communicate at hardware speed using a purpose-built protocol.
The mental model shift here is from "How do I connect services?" to "How do I eliminate every unnecessary CPU cycle and millisecond of delay between the physics of the wire and my application?"