topic / networking
Networking
The distance between two machines, in packets.
DNS, TCP, TLS, HTTP — the protocol stack that carries every request. We trace each layer's job, its cost, and the failure modes you only discover under load.
3 articles · 2 videos · 5 total
Articles
How HTTP/2 and HTTP/3 Change Everything
Multiplexing, server push, and QUIC — why keep-alive is the old answer and what the new protocols actually fix.
What Happens When You Call an API?
One request, traced end to end: DNS, TCP, TLS, HTTP, load balancing, server logic, and the database — with the real cost of every hop.
How TLS Actually Secures a Connection
From the ClientHello to the session ticket: what every message in a TLS handshake does, why certificates are the center of the trust model, and how TLS 1.3 changed the game.
Videos
HTTP/3 and QUIC Explained
The transport protocol that replaces TCP — multiplexing without head-of-line blocking, connection migration, and 0-RTT.
WatchThe Full Lifecycle of an HTTP Request
Watch a single request travel from a browser through DNS, TCP, TLS, HTTP, a load balancer, a server, and a database — with live packet-level tracing.
WatchExplore adjacent
Depth, delivered weekly
One technical dispatch a week on networking and the systems around it.
One technical dispatch per week. No noise.