Blog

A WebSocket message is eleven bytes on the wire, and almost everything written about those bytes is checkable against a real socket in about a second.

You've read "Node.js is single-threaded and non-blocking." Fine. But that sentence raises more questions than it answers. If it's single-threaded, who's doing the file I/O while your JavaScript runs?

From BGP Anycast routing to tiered cache hierarchies and Surrogate-Key purge — how CDNs actually move traffic from your origin to the nearest edge server.

Your Node.js server calls res.send("hello") and somewhere, 1400 bytes cross the planet in 80 milliseconds and appear correctly in a browser. That's wild. But what actually happens?

HTTP/2 replaces ASCII text with a binary framing layer and multiplexes dozens of requests over one TCP connection. Here's what actually happens at the wire level.

DNS translates domain names to IPs via a hierarchical delegation tree. Here's what actually happens between typing a URL and your browser connecting.