Chapter 4: Networks — Connecting the System of Systems

Networks — Connecting the System of Systems 🌐

How devices, protocols, and the Internet turn separate machines into one connected world.

You send a message to a friend on the other side of the planet, and it arrives in about a second. In that heartbeat, your words were chopped into tiny pieces, stamped with addresses, handed from machine to machine across oceans, checked for errors, and reassembled in the right order on your friend’s screen. No single company owns the path it took, and no human steered it. So how does it work? The answer is one of the most powerful ideas in all of computing: separate machines can act as one system when they agree to follow the same rules.

4.1 — From One Machine to a Network of Networks

A single computer is powerful, but a network is far more powerful. When devices connect, they can share files, printers, games, and access to the Internet.

Networks come in different sizes. A LAN connects devices in one place, like the computers, tablets, and printer in your classroom. A WAN connects networks across cities or countries. The Internet is the biggest WAN of all — it is not one giant network but a “network of networks,” millions of separate LANs and WANs agreeing to connect to one another.

Type	Area Covered	Example	Who Runs It
LAN	One room or building	Your school’s Wi-Fi	The school
WAN	City, country, or larger	A company’s offices linked across states	The company or an ISP
Internet	The entire globe	The whole web	No single owner — cooperating networks

The magic is that these networks were built by different people, in different countries, at different times — yet they interconnect. That only works because they all speak a common language.

4.2 — Protocols: The Rules That Let Strangers Talk

A protocol is an agreed-upon set of rules for communication. Think about mailing a letter. There are unwritten rules everyone follows: put the address on the front, the return address in the corner, a stamp in the top right. You have never met your mail carrier, but because you both follow the same postal rules, your letter arrives. A protocol is exactly that kind of agreement, but for computers.

Protocols matter because the devices on a network are wildly different — a phone, a laptop, a smart thermostat, a massive server. They run different software and were made by different companies. Without shared rules, they would be like people shouting in languages no one else understands. With protocols, a Windows laptop and an Android phone can exchange data perfectly, because both agree on the format and order of the conversation.

4.3 — Addresses, Packets, and Routing

For data to reach the right place, every device needs an address. An IP address (Internet Protocol address) is a unique number that identifies a device on a network, much like a mailing address identifies a house. An address like 142.250.72.14 tells the network exactly where to deliver data.

But data usually isn’t sent all at once. Instead it is broken into small chunks called packet s. Each packet carries a piece of the message plus a “header” listing where it came from and where it’s going. Splitting a big file into packets means a slow packet doesn’t block everything else, and packets can even take different paths to the same destination.

Steering those packets is the job of the router . A router reads each packet’s destination address and forwards it one hop closer to its goal, like a chain of postal sorting centers. This process of choosing a path is called routing. A single packet might pass through a dozen routers on its journey across the world.

4.4 — The Protocol Stack: Rules Working in Layers

No single protocol does everything. Instead, protocols work in layers, each handling one job and trusting the layer below it — much like the postal system separates “writing the letter” from “driving the truck.” This layering is often called the protocol stack.

Two protocols do the heavy lifting for most Internet traffic. IP handles addressing and getting packets to the right place. TCP (Transmission Control Protocol) sits on top of IP and makes delivery reliable: it numbers the packets, waits for the receiver to send back an acknowledgement (“got it!”), asks for a resend if a packet is lost or damaged, and reassembles everything in the correct order. Together they are often written as TCP/IP.

Here are the key protocols you meet every day:

Protocol	What It Does	Everyday Example
IP	Addresses and routes packets	Getting data to the right device
TCP	Reliable, in-order delivery with error checks	Loading a full web page without missing pieces
HTTP / HTTPS	Requests and delivers web pages (HTTPS is encrypted)	Visiting a website in your browser
DNS	Turns names into IP addresses	Typing `google.com` instead of a number

4.5 — DNS: The Internet’s Phonebook

Humans remember names; computers use numbers. You type wikipedia.org, but your device needs an IP address to actually connect. The DNS (Domain Name System) bridges that gap. It works like a giant, shared phonebook: you look up a name, and DNS hands back the matching number.

Every time you visit a website, your device quietly asks a DNS server, “What’s the IP address for this name?” The server replies, and only then can the real conversation begin. Without DNS, you’d have to memorize strings of numbers for every site you visit — which is exactly why it was invented.

4.6 — Bandwidth vs. Latency: Two Ways to Measure Speed

People say a network is “fast,” but that hides two very different ideas. bandwidth is how much data can flow at once — think of it as the width of the pipe. latency is how long a single trip takes — the delay before data starts arriving.

An easy way to keep them straight: bandwidth is how many lanes the highway has; latency is how long the drive takes. A wide highway (high bandwidth) still feels slow if every trip has a long delay (high latency).

Concept	Measures	Units	Highway Analogy
Bandwidth	How much data per second	Mbps / Gbps	Number of lanes
Latency	Delay for the trip	Milliseconds (ms)	How long the drive takes

This distinction is real. Streaming a movie needs high bandwidth to move all that video. Playing a fast online game needs low latency so your button press registers instantly. A connection can be great at one and poor at the other.

4.7 — Physical vs. Wireless Connections and Topologies

Protocols decide the rules, but data still needs a physical path. Wired connections use cables. Ethernet cables and fiber-optic cables (which send data as pulses of light) are fast and stable. Wireless connections skip the cable: Wi-Fi links devices over radio waves inside a building, and cellular networks (like 4G and 5G) connect your phone over long distances through cell towers.

Neither is simply “better.” Wired connections are usually faster and more reliable; wireless connections are more convenient and let devices move around freely.

Networks are also arranged in different shapes, called topologies, and the shape a network takes affects how reliable it is. The most common arrangement in homes and schools is the star, in which every device connects to one central point such as a switch or router; all traffic passes through that hub. A mesh works differently, wiring devices to many others at once, so that if one path fails the data simply reroutes around it — the Internet as a whole behaves like a giant mesh for exactly this reason. Simplest of all is the bus, or line, where every device shares a single connection line; it is easy to set up but easily disrupted, since a break in that one line can take down the whole network.

Chapter Activity: Trace a Web Page’s Journey 🕵️

In this activity you’ll model how protocols cooperate to load a single web page — directly practicing standard 2-NI-04 (modeling the role of protocols in transmitting data).

Part 1 — Map the protocols. With a partner, put these five steps in the correct order and name the protocol doing each job: (a) the page’s text and images arrive reliably and in order; (b) your browser asks the server to send the page; (c) your device looks up the site’s IP address from its name; (d) packets are routed hop-by-hop to the server; (e) the connection is encrypted so no one can read it.

Answer key: c → DNS, d → IP, b → HTTP, a → TCP, e → HTTPS.

Part 2 — Simulate a packet’s journey. Split into roles: Sender, three or four Routers, and Receiver. The Sender writes a one-sentence message, splits it into 3–4 sticky notes (“packets”), and numbers each one and writes the Receiver’s name (the “IP address”) on it. Hand the packets to Routers, who pass them along — deliberately deliver them out of order, and have one Router “drop” a packet.

At the Receiver, use TCP rules: check the numbers, notice the missing packet, and send an “acknowledgement” back requesting a resend. Only once all packets arrive, reassemble the message in numbered order.

Discuss: Which protocol caught the missing packet? Why does numbering matter? What would happen with no shared rules at all?

Key Concepts Checklist

Looking Ahead

You now understand how devices connect and how protocols move data across the world. But that same openness raises a big question: if data can travel anywhere and no one owns the whole path, how do we keep it safe and keep systems working when things go wrong? In Chapter 5 — Designing for Security and Reliability, we’ll explore encryption, protecting data in transit, and how engineers design networks that keep running even when parts fail.