HotThe RequestLayersNamesRoutesLatencyWireless
Latest Every page you open is a short journey with several places it can go wrong.
Opening Note

What Really Happens Between Typing A Name And Seeing A Page

The gap between pressing enter and watching a page appear feels like nothing at all. It is not nothing. It is a sequence, and once you can name the steps you can think clearly about all of them.

Most people meet the internet as a single smooth surface. You type a name you remember, you wait a moment, and words and pictures arrive. Because the whole thing succeeds so often, it presents itself as one action. It is not one action. It is a short chain of separate jobs, each done by a different piece of machinery, each capable of finishing quickly or slowly or not at all. The purpose of this issue is to slow that chain down and give you a name for every link in it. Nothing here requires you to be technical. It requires only that you accept that the smooth surface has parts underneath, and that the parts are knowable.

Start with what you actually typed. You typed a name, and a name is a human convenience. It is chosen so that people can remember it, say it aloud and print it on the side of a van. The machinery that carries your request does not use names. It uses addresses, which are chosen so that equipment can sort them quickly and consistently at enormous volume. So the very first job in the chain is a translation: something has to turn the name you remember into the address the network can act on. That translation is a lookup, it happens across a distributed system of helpers scattered around the world, and like every lookup it can be fast, slow, stale or simply unanswerable.

Continue reading

The Journey Of A Request

Why Your Device Only Knows One Step Ahead

The machinery carrying your message never holds a picture of the whole route.

Cut Into Pieces, Carried Separately, Put Back Together

Your message does not travel whole, and that is a feature rather than a compromise.

Layers As A Way Of Thinking

Thinking In Layers Turns Panic Into A Checklist

Work outward from yourself and let each answer narrow the next question.

How Restraint At The Centre Made Change Possible

The network was kept simple so that the edges could be clever.

Addresses, Names And Routes

Why The Same Name Reaches Different Machines

Ask for the same name from two cities and you may be answered by two different places.

What A Router Is Actually Deciding

Strip away the mystique and the decision is small, repeated and local.

Why It Is Slow Or Broken

Congestion, Queues And The Cost Of Waiting In Line

When more arrives than can leave, something has to wait, and waiting is the delay.

Wireless Is Shared Air And Everything Nearby Is In It

The most convenient part of the chain is also the least predictable.

About Networking Kid

Networking Kid exists for one kind of reader: the capable adult who uses the internet constantly, has never been taught how it works, and has quietly concluded that the explanation must be beyond them. It is not. The ideas that make a network move a message are genuinely elegant and genuinely learnable, and almost none of them require mathematics, equipment or prior study. What they require is somebody willing to explain them in order, without jargon used as a gate, and without the faint condescension that so often accompanies technical writing aimed at people who are meeting the subject for the first time.

The name is informal on purpose. It is meant to signal curiosity rather than expertise, the willingness to ask the obvious question that everyone else in the room is too proud to ask out loud. There is no assumption here that you know anything in advance, and no assumption whatsoever that you are less intelligent for not knowing it. The material is written the way a patient friend would explain it over a long coffee: one idea at a time, each one earning its place before the next arrives, with the connections between them made explicit rather than left as an exercise for the reader.

The scope is deliberately narrow, because a narrow subject explained properly is worth more than a broad one skimmed. This publication is about how a network carries a message from one place to another: the translation of names, the finding of routes, the separation of concerns that lets the carrying part ignore the meaning part, and the ordinary physical realities that make things slow or unreliable. It is not a guide to defending systems, nor a manual for running technology in an organisation, and it offers no instructions for touching any network other than your own. The aim is understanding rather than intervention, because understanding is what actually lasts.