Amit Dhotay Posted on May 31 deep dive into network protocols # programming # architecture Most people never think about network protocols, and that is exactly how it should be. Protocols are the invisible agreements that let billions of devices, built by competing companies and running incompatible software, cooperate well enough to load a web page. They only become visible when they fail and when they fail at scale, the failure is spectacular. This article walks through the four protocols that carry almost everything you do online: IP and TCP : which move and order the bytes; BGP : which decides which path those bytes take across the planet; DNS : which turns human-friendly names into machine addresses; HTTP/HTTPS : the language the web itself speaks. Then it tells the story of October 4, 2021, when a single change to one of these protocols took Facebook, Instagram, and WhatsApp off the internet for roughly six hours a case study that shows, better than any diagram, how tightly these layers depend on one another. A protocol is just an agreement A protocol is a shared set of rules for how two parties exchange information what a message looks like, what order things happen in, and what to do when something goes wrong. Network protocols do the same thing, just formalized down to the bit. The internet is built as a stack of these agreements, each handling one job and trusting the layer below it to handle its own. The mental model worth holding onto is this: lower layers move raw data between machines, and higher layers add meaning. The beauty of this design is separation of concerns: your browser speaking HTTP does not need to know whether your packets travel over fiber, copper, or radio. But the cost of that design is dependency. Each layer assumes the one beneath it is working. When a low layer breaks, everything above it breaks too and the symptoms often appear at the top, far from the real cause. Hold that thought; it is the whole point of the case study. IP and T
LIVE