Networking essentials: what a request actually crosses
Every box on your diagram is joined by an arrow, and every arrow is a network hop with a handshake, a round-trip time and a failure mode; this lesson prices those arrows, from DNS and the TCP and TLS handshakes to HTTP versions, load balancers, timeouts and the speed of light between regions.
What you'll be able to do
- Count the round trips a new and a reused connection cost, and turn them into milliseconds for a near and a far client
- Choose TCP or UDP, and HTTP/1.1, HTTP/2 or HTTP/3, for a stated reason rather than by habit
- Place a layer 4 or layer 7 load balancer, pick a balancing algorithm and say what its health check actually proves
- Set timeouts, keep-alive and connection pools so that one slow dependency cannot exhaust a fleet
Before this: back-of-the-envelope
Log in to read the rest of this lesson
Every box on your diagram is joined by an arrow, and every arrow is a network hop with a handshake, a round-trip time and a failure mode; this lesson prices those arrows, from DNS and the TCP and TLS handshakes to HTTP versions, load balancers, timeouts and the speed of light between regions. This walkthrough runs about 22 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.
Log in to continueThe first module of every track is free to read on the web: see what's open in System design.