networking
Networking & Protocols
From bits on a wire to TLS 1.3 — the journey of one packet, retold for senior engineers.
Start track →Start from zero
Before the senior material: what a network even is, and the handful of words the rest of the track assumes you already know.The physical link
How bits become electricity, light, or radio — and what limits them.IP packets: addressed envelopes
How a packet finds its way across millions of independent networks, what the IP header carries, and where datagrams die.The TCP handshake
What SYN, SYN-ACK, and ACK actually negotiate — and why a connection's first RTT decides the speed of every request on it.DNS: from name to address
How a recursive resolver climbs the root → TLD → authoritative tree to turn google.com into an IP, and where caches and DNSSEC live.TLS 1.3: keys and confidentiality in one RTT
How ClientHello key shares plus a certificate verifier collapse the old TLS 1.2 two-RTT handshake into one — and what 0-RTT actually buys you.HTTP versions: from 1.1 to 3
How HTTP evolved from serial request-response to multiplexed streams to QUIC datagrams — and what each version costs to run in production.CDN and edge delivery
How edge servers, cache hierarchies, and smart routing cooperate to deliver content in 20 ms instead of 200 ms — and what breaks when any layer is misconfigured.WebSocket and real-time
How WebSocket upgrades an HTTP connection to a persistent full-duplex channel — and everything that breaks when 10,000 slow clients pile into one broadcast server.Proxy and load balancing
A reverse proxy opens two TCP connections per request so it can route, health-check, and scale backends invisibly — and every load balancing decision from round-robin to consistent hashing is a tradeoff between speed, fairness, and state.QUIC internals
QUIC fuses UDP, TLS 1.3, and multiplexed streams in user space — giving 1-RTT handshakes, HoL-free streams, and connection migration, at the cost of 15–30% more CPU per byte than kernel TCP.Network security
DDoS attacks, amplification floods, and infrastructure-layer hijacks (DNS/BGP) are defeated by layered defenses — anycast edge absorption, rate limiting, WAF, mTLS, and RPKI/ROV — because no single defense stops all vectors.Putting it all together
Every layer from DNS to circuit breaker fires on every request — the capstone chapter shows how they compose, fail, and recover as a system.Build with this track
Guided projects that exercise what you learn here.
Collaborative cursors
Show every connected user's live cursor and selection in a shared document, conflict-free, over WebSocket.
Feature-flag service
Build a small flag service with targeting rules, percentage rollouts, and a typed SDK that evaluates flags client-side from a cached ruleset.
Homelab Secure Stack
Stand up a self-hosted media and home-server stack on nas01.example where five services share a single VPN container's network namespace — the kill-switch drops all traffic the moment the tunnel dies, a split-tunnel whitelist carves out LAN access, and three layered access rings (localhost / LAN 10.0.0.0/24 / mesh-VPN 100.64.0.30) keep the right doors open to the right people. Harden the host with SSH key-only auth, fail2ban, and unattended security upgrades; write a rotating, age-encrypted off-site backup; and walk away knowing the stack stays dark if anything breaks.
Browser & Frontend Runtime
What actually happens inside the browser when your page loads and runs — how JavaScript is scheduled, how pixels get drawn, and where the slow parts hide.