Networking
TCP/QUIC, DNS, CDN — how data actually arrives
01
·Networking·FREE·11 min read
From TCP to QUIC — Reinventing Reliable Communication
The internet is built on a foundation that makes no promise of delivery. This piece starts from zero: how TCP manufactures reliability out of sequencing, retransmission and congestion control, why HTTP/2 hit a wall, and why QUIC deliberately rebuilt all of it on top of UDP.
02
·Networking·★ MEMBER·11 min read
DNS and CDNs — What Happens Between Enter and Pixels
In the second or so between pressing Enter and seeing a page, a name gets resolved down a tree, four layers of cache get consulted, and an edge server somewhere near you answers instead of the origin. Here is how DNS walks that tree, what a TTL does not promise, and how a CDN talks its way around the speed of light — from zero background.
03
·Networking·★ MEMBER·8 min read
HTTP/1.1 → 2 → 3 — The Road to Multiplexing
Thirty years of HTTP is really one argument: how many conversations can share a single connection? Why 1.1's one-at-a-time rule created traffic jams, what HTTP/2 solved with frames and streams, why the jam simply moved one floor down, what HTTP/3 separated by swapping the foundation — and how to measure your own network before picking one.