What is a network, really?
Why computers need to talk to each other at all, and the one simple idea sitting underneath every network you have ever used.
Passing notes in class
Imagine you are five years old, sitting in the back of a classroom, and you want to tell your friend on the other side of the room "meet me at lunch." You can't shout it, so you write it on a piece of paper and pass it hand to hand until it reaches your friend.
That tiny scene already has every piece a computer network needs:
- Two people who want to talk — this is a computer, a phone, a smart TV. We call it a node.
- A path the paper travels along — the chain of hands. We call this a link.
- An agreement on how to pass it — everyone knows to pass it forward, not read it out loud, not eat it. We call this a protocol.
A computer network is nothing more than nodes connected by links, following protocols. Every fancy term you'll meet in this course — routers, IP addresses, TCP, Wi-Fi — is just a more precise version of "pass this note correctly."
Why not just shout?
Shouting works if your friend sits right next to you (one room, a few nodes) but breaks down instantly at scale. You can't shout across a city, and even if you could, everyone shouting at once turns into noise nobody can understand.
Networks solve this with structure: small groups of nearby nodes are wired together into a LAN (Local Area Network — think one classroom, or one house), and LANs are then connected to each other over longer distances into a WAN (Wide Area Network — think the road connecting two cities). The Internet is simply the WAN of all WANs: a network of networks, with no single owner, held together purely by everyone agreeing to use the same protocols.
Your laptop ── Wi-Fi ── Home router ── ISP ── ISP ── Server in another country
(node) (LAN) (WAN, "the Internet")
Two ways to send a message
Say you want to talk to your friend on the phone, or you want to mail them a letter cut into three postcards. These are the two founding ideas of networking:
Circuit switching — like a phone call. Before you say a word, the phone company reserves a dedicated path just for you, start to finish. Nobody else can use that exact path while you're talking, even during the silent pauses. This is simple and gives predictable quality, but wastes capacity whenever you're not actively sending anything.
Packet switching — like cutting your letter into numbered postcards and mailing them separately. Each postcard (called a packet) carries a small piece of the message plus a label saying "postcard 2 of 3, headed to this address." The postal system can mix postcards from thousands of different letters on the same truck, because each one carries its own address. The Internet is built almost entirely on packet switching, because it lets millions of people share the same wires efficiently.
The math behind splitting a message
Suppose you want to send a 1500-byte photo, and your network only allows packets up to 500 bytes of actual data (this ceiling is called the MTU, Maximum Transmission Unit). How many packets do you need?
The symbol means "round up" — even a 1501-byte message needs 4 packets, because a packet can't be split further once it's already the smallest unit you're sending.
But packets aren't free — each one carries a header full of addressing information, say 20 bytes for this example. So the actual data sent over the wire is:
That extra 60 bytes is overhead — the "cost" of using addressed postcards instead of one continuous phone call. This trade-off, a little bit of overhead in exchange for being able to share the wire with everyone else, is the central bargain the whole Internet is built on.
Common mistakes
- Thinking "network" means "the Internet." The Internet is one enormous, specific network. Your home Wi-Fi is also a network, and so is the pair of walkie-talkies your parents used on a road trip.
- Assuming packet switching is always better. Circuit switching still shows up where predictable, unbroken quality matters more than efficiency — old telephone systems and some real-time audio links use it.
- Forgetting overhead exists. Every packet you send carries "invisible" header bytes. On very small messages, headers can be a bigger cost than the actual data.
Summary
A network is just nodes talking over links using agreed-upon protocols. Small local networks (LANs) connect into larger ones (WANs), and the Internet is the network of all networks. Messages are usually split into small, individually addressed packets rather than sent over one dedicated line, because sharing capacity this way lets an enormous number of people use the same wires — at the small, calculable cost of header overhead on every packet.