Most explanations of network infrastructure hand you a glossary. Router, switch, firewall, load balancer, here's what each one does, memorize it. Which is fine until you're actually designing or debugging something and realize a parts list doesn't tell you how any of it fits together or, more importantly, why it's laid out the way it is. So let me give you the mental model instead, because once it clicks, the components explain themselves.
Everything is about moving packets and deciding who's allowed
Strip it all down and a network does two jobs: get data from A to B efficiently, and control who's allowed to talk to whom. Every device is serving one or both of those. Switches and routers are the "move it efficiently" job, at different scopes. Firewalls and segmentation are the "control who talks to whom" job. When you're staring at an unfamiliar network, sorting each piece into "is this moving traffic or governing traffic" cuts through most of the confusion immediately.
*Switch vs router, the version that actually sticks
*
A switch connects devices within a network, your local segment, and moves traffic between them fast. A router connects different networks to each other and decides how traffic gets from one to another, including out to the internet. The one-liner: switches are within, routers are between. Most "why can't these two machines talk" problems come down to whether they're on the same segment (a switch's job) or different ones (a router's job, plus whatever's allowed to cross).
Segmentation is the idea that actually matters for security
Here's the concept worth more than the whole parts list. You don't want one big flat network where everything can reach everything. You want it divided into segments, with controlled crossings between them, so that a problem in one place can't automatically reach everywhere else. Your payment systems shouldn't sit on the same flat network as the guest wifi. The database tier shouldn't be freely reachable from every laptop in the building.
The reason this matters so much: most damage in a breach isn't the initial break-in, it's the lateral movement afterward. Someone gets a foothold on one machine, and if your network is flat, they can reach everything from there. Segmentation is what turns "they got in" from a catastrophe into a contained incident. It's the single highest-leverage design decision in a network, and it's conceptual, not a box you buy.
*Redundancy is a design property, not a feature
*
Networks fail. Cables, devices, links, they all die eventually. Redundancy means no single failure takes the whole thing down: multiple paths, backup devices, no chokepoint whose death is fatal. The thing to internalize is that redundancy has to be designed in from the topology up, not sprinkled on later. If your whole network depends on one device, you don't have a network, you have a single point of failure with extra steps.
Where modern reality complicates the tidy picture
The classic model assumes a clear inside and outside, one perimeter to defend. That's increasingly fiction. Your stuff is in the cloud, your people are remote, SaaS is everywhere, and there's no single edge anymore. So the modern version of "control who talks to whom" leans less on the network perimeter and more on identity, verifying who and what is making each request rather than trusting anything just because it's "inside." The components still exist, but the trust model built on top of them has shifted, and designs that still assume a solid perimeter are solving last decade's problem.
The useful way to hold all this
Don't memorize the parts. Understand the two jobs (move traffic, govern traffic), understand that segmentation is your main defense against lateral movement, understand that redundancy is topological, and understand that the old inside/outside model is fading in favor of verifying identity everywhere. Hang the components on that frame and they stop being a glossary and start being a design language you can actually think in.
The parts list is easy to look up. The model is the part worth carrying around in your head.
