Network Types and Topologies
LAN to WAN to SAN — and Bus to Star to Mesh. The two dimensions that define every network ever built, and why the layout you choose on day one determines what breaks on year five.
Quick answer
Networks are described on two independent axes. Type is about scope and ownership: PAN, LAN (one site, you own it), MAN, WAN (many sites, usually leased) and SAN. Topology is about the shape of the connections: bus, star, ring, mesh or tree.
- Star is the modern LAN standard: every device connects to a switch.
- A full mesh is the most resilient and the most expensive.
- Bus topology survives only in embedded systems such as a car's CAN bus.
for devices in (5, 10, 50):
star = devices # each device to one central switch
mesh = devices * (devices - 1) // 2 # every pair directly connected
print(f"{devices:>2} devices: star {star:>3} links, full mesh {mesh:>4} links")Output
5 devices: star 5 links, full mesh 10 links 10 devices: star 10 links, full mesh 45 links 50 devices: star 50 links, full mesh 1225 links
// CHAPTER 01
The Decisions That Haunt You at 2 AM
Every network failure can be traced back to a design decision made years earlier.
// REAL-WORLD SCENARIO
This is what topology decisions actually cost. The engineer who wired that building in 2014 chose the cheapest option — one switch per floor, connected in a chain. No redundancy. No alternative paths. Nobody asked "what happens if this one switch dies?" That question should have been answered on day one.
This lesson gives you two frameworks for classifying and designing networks. The first is network type — how geographically large is this network, and who owns it? The second is topology — what shape does the physical wiring take, and how does that shape determine resilience, cost, and scale? These are not academic classifications. They are the vocabulary you need to design networks that survive reality.
🎯 The two questions every network designer must answer
// CHAPTER 02
Network Types — Classified by Geographic Scope
From the Bluetooth in your ear to the fiber under the Pacific Ocean.
The most fundamental way to classify a network is by geographic scale. Engineers use these terms constantly — in job descriptions, architecture diagrams, vendor docs, and incident reports. Understanding what each acronym actually means (not just the expansion) saves you from confusion in every technical conversation.
Interactive — Network Types
Click any network type to explore its scale, speed, ownership, and real-world examples.
The office you work in almost certainly has a LAN. Every laptop connected to WiFi, every printer, every IP phone — all part of the same LAN. Traffic between them never leaves the building.
Real-world examples
The Lines Are Blurring — Cloud Changed Everything
These categories were crisp in 1990. Today, they blur in fascinating ways. When your startup team connects via WireGuard VPN to a private subnet on AWS, is that a LAN or a WAN? Technically, it is a WAN traversal (traffic crosses the internet) that behaves exactly like a LAN — same private IP subnet, no NAT, sub-10ms latency. AWS calls this a VPC (Virtual Private Cloud), and it deliberately gives you LAN semantics over WAN infrastructure.
Similarly, when you use SD-WAN (Software-Defined WAN), you are abstracting the physical WAN links (MPLS, broadband, LTE) into a single logical network managed by software. A branch office in Denver and a headquarters in Chicago appear to be on the same "flat" network — but the physical connection might be switching between MPLS and LTE depending on cost and latency. The topology is virtual, not physical.
// REAL-WORLD SCENARIO
When to Use What
LANMAN or CANWANSANPAN (Bluetooth) + LAN (WiFi)// CHAPTER 03
Physical Topologies — The Shape of Your Network
How devices are wired together determines what can fail, how fast data travels, and how much it costs.
// REAL-WORLD SCENARIO
Physical topology describes how devices are physically wired to each other — the actual shape of the cables. There are six fundamental topologies. Every real-world network is built from some combination of them.
Interactive — Topology Explorer
Select a topology to see its structure, strengths, weaknesses, and failure behavior.
Every device connects to one central hub or switch. No direct device-to-device links. Almost all modern networks use this.
// CHAPTER 04
Bus Topology — The Network That Taught Us What Not to Do
Understanding why it was built the way it was, and why it disappeared.
In the early 1980s, a coaxial cable ran through an office building and every computer was physically clamped to it with a vampire tap — a connector that pierced the cable shielding to make contact. This was 10BASE5 (Thick Ethernet), and it was revolutionary. One cable, unlimited devices, no dedicated hardware beyond the cable itself. By 1985, it evolved to 10BASE2 (Thin Ethernet, BNC connectors) which you could wire yourself with cheap coaxial cable.
The fundamental problem was collision domains. Since all devices shared the same wire, only one device could transmit at a time. If two devices transmitted simultaneously, their signals collided and destroyed each other — both had to wait a random interval and retry. This is called CSMA/CD (Carrier Sense Multiple Access with Collision Detection). As devices were added, collisions multiplied, performance dropped. A 10 Mbps bus with 20 devices might only deliver 2-3 Mbps effective throughput.
The single biggest failure mode of bus topology was physical: one break, everyone goes down. A cable cut, a bad connector, even a loose BNC terminator at either end — and every device on the bus lost connectivity instantly. There was no alternative path. Network troubleshooting in the bus era involved walking the entire cable run with an ohmmeter looking for a break. Engineers who grew up in this era still flinch at coaxial cable.
✗ Common Mistake — Bus topology is still used in modern networks
// CHAPTER 05
Star Topology — Why Every Network Today Looks Like This
The switch changed everything. Here is why star topology won and how it actually works at scale.
// REAL-WORLD SCENARIO
Today, virtually every network — from your home WiFi (all devices connect to one router) to Google's data centers (all servers connect to a Top-of-Rack switch) — is a star at its core. The key innovation was replacing the hub with a switch.
Hub vs Switch — A Critical Distinction
Both create a star topology, but they behave completely differently:
- Repeats every incoming signal to ALL ports
- All devices still share one collision domain
- Half-duplex only (can't send and receive at once)
- 10 Mbps shared among all ports
- Everyone sees everyone else's traffic
- Dead for new installations (ca. 2000)
- Learns MAC addresses, forwards only to correct port
- Each port is its own collision domain
- Full-duplex (send and receive simultaneously)
- Each port gets dedicated bandwidth (1–100 Gbps)
- Traffic is private between source and destination
- Standard for all modern networks
When data arrives at a switch port, the switch reads the destination MAC address from the Ethernet frame header and looks it up in its MAC address table (also called the CAM table — Content Addressable Memory). If it knows which port that MAC is on, it forwards the frame only to that port. If it does not know yet (no entry in the table), it floods the frame to all ports except the one it came from — and then learns from the response.
Spanning Tree Protocol — Preventing Loops
A star topology with redundant switches creates a problem: loops. If Switch A is connected to Switch B, which is connected to Switch C, which is connected back to Switch A, a broadcast frame would loop forever — a broadcast storm that consumes 100% of bandwidth and crashes the network within seconds.
STP (Spanning Tree Protocol — IEEE 802.1D) prevents this by logically blocking redundant paths. STP elects a root bridge, calculates the shortest path from every switch to the root, and puts redundant paths in blocking state. If the active path fails, STP unblocks an alternative path — but this takes 30–50 seconds with classic STP. Modern networks use RSTP (Rapid Spanning Tree — 802.1w) which converges in 1–2 seconds, or port channel/LAG aggregation which bonds multiple links without needing STP at all.
💡 Why your network switch restarts slowly after a power cut
// CHAPTER 06
Ring Topology — Deterministic and Resilient When Done Right
Token Ring is dead, but ring topology lives on in backbone networks carrying national telephone traffic.
Ring topology was IBM's answer to Ethernet's collision problem in 1984 — Token Ring (IEEE 802.5). Instead of random collision detection, a special packet called a token circulated around the ring. Only the device holding the token was allowed to transmit. Deterministic access: no collisions, equal fairness, predictable performance. But Token Ring was slow to expand (adding a device required breaking the ring), expensive (IBM's MAU — Multistation Access Unit — cost a fortune), and fundamentally lost the market to switched Ethernet by 1998.
Token Ring died. Ring topology did not. The world's telephone networks and long-haul internet backbone still use ring topology in the form of SONET/SDH (Synchronous Optical Networking / Synchronous Digital Hierarchy) — the standard physical layer for carrier networks since the 1990s.
Dual-Ring Self-Healing — How SONET Achieves 99.999% Uptime
The weakness of a simple ring — one break = total failure — is solved by running two rings in opposite directions simultaneously. This is the SONET/SDH BLSR (Bidirectional Line-Switched Ring) architecture.
The 50ms protection switching time of SONET/SDH is a standard specification — the ITU requires it for carrier-grade networks. This is tight enough that voice calls don't experience audible disruption. For comparison, a human typically does not notice audio interruptions under 200ms. Modern networks use OTN (Optical Transport Network) which extends SONET concepts with more capacity and better overhead management.
// CHAPTER 07
Mesh Topology — Why the Internet Never Goes Down
The internet is a global partial mesh of 80,000 autonomous systems. Here is how routing works in a mesh.
// REAL-WORLD SCENARIO
The internet is the world's largest mesh network — specifically, a partial mesh of ~80,000 Autonomous Systems (ASes) connected by BGP peering relationships. No single AS connects to every other AS (that would be a full mesh requiring billions of physical links). Instead, each AS connects to a few well-chosen peers, and BGP propagates reachability information so every AS can eventually reach every other.
Full Mesh vs Partial Mesh
In data centers, the dominant topology today is spine-leaf — a two-tier partial mesh. Every leaf switch (ToR — Top of Rack) connects to every spine switch. No leaf connects directly to another leaf. This creates equal-cost multi-path routing (ECMP) — traffic from any server to any other server takes exactly 2 hops through the fabric, and there are always multiple equal-cost paths to load-balance across.
📐 Why Clos networks are mathematically elegant
// CHAPTER 08
Tree Topology — The Enterprise Network Standard
How Fortune 500 companies wire tens of thousands of devices across dozens of floors and buildings.
When a company needs to connect 5,000 employees across a 20-floor office building, star topology at one level is not enough. You need a hierarchy — a tree of star networks, where each level aggregates the bandwidth from the level below.
The Three-Tier Enterprise Model
2–4 high-end switches (Cisco Catalyst 9500, Juniper EX9200)4–20 switches (Cisco Catalyst 9300)20–200 switches (Cisco Catalyst 9200)The critical insight of the three-tier model is traffic locality. Most office communication stays within a department — emails, file shares, printers. By organizing the tree so that each department is under the same distribution switch, most traffic never needs to go higher than the distribution layer. Only inter-department or internet traffic climbs to the core. This is why enterprise networks can handle 10,000 devices with only a handful of core switches.
Collapsed Core — For Smaller Networks
For networks under ~500 devices (small offices, branch offices), the distribution and core layers merge into a single collapsed core layer. Two high-performance switches handle everything that distribution and core would normally split. This reduces hardware cost while maintaining the essential isolation that access layer star topology provides.
// CHAPTER 09
Hybrid Topology — What Real Networks Actually Look Like
No production network of any size is a single pure topology. They are all hybrids.
Pure topologies exist in textbooks. Real networks combine multiple topologies at different scales, choosing the right shape for each requirement. Understanding this is what separates someone who can recite topology names from someone who can design real infrastructure.
A Real Enterprise Network Architecture
Notice how each layer uses the appropriate topology: star for end-device connections (simple, manageable), tree for building-scale aggregation (hierarchical, scalable), partial mesh for building-to-building (redundant), ring for long-haul backbone (self-healing), and mesh peering for internet connectivity (maximum resilience).
// CHAPTER 10
Modern Topology Trends — How Networks Are Evolving
Software-defined networking, the cloud, and intent-based networking are changing how topology decisions are made.
SD-WAN — Topology as Software
SD-WAN (Software-Defined Wide Area Network) abstracts the physical WAN topology from the logical network. Instead of manually configuring MPLS circuits between offices, SD-WAN creates a virtual full mesh — any branch can talk directly to any other branch over whatever physical links are available (MPLS, broadband, 4G/5G, satellite). The SD-WAN controller decides in real-time which physical path each traffic flow should take based on latency, packet loss, and cost.
A branch office in Tulsa might send Zoom video directly to a branch in Charlotte via broadband (low cost, acceptable latency), while SAP traffic goes via MPLS (guaranteed QoS, predictable latency), and backup data goes via LTE (expensive per MB, but available when MPLS is down). The topology is virtual, dynamic, and policy-driven. Cisco Viptela, VMware VeloCloud, and Fortinet Secure SD-WAN are the major vendors.
Leaf-Spine Goes Mainstream
The three-tier enterprise model (core/distribution/access) was designed for north-south traffic — client to server, up and down the hierarchy. Modern workloads are increasingly east-west — server to server, microservice to microservice, container to container. The three-tier model is inefficient for east-west: traffic from any server to any other server has to climb to the core and back down.
Leaf-spine (spine-leaf) topology solves this: every server is always exactly two hops from every other server, regardless of which leaf they are on. As workloads shift from client-server to microservices, leaf-spine is replacing three-tier even in enterprise data centers. If you are designing a new data center today, leaf-spine is the answer.
Intent-Based Networking (IBN)
Traditional networks are configured device by device, command by command. Intent-Based Networking lets you declare what you want ("all HR computers should not be able to talk to engineering servers") and software translates that into thousands of ACL rules, VLAN assignments, and routing policies automatically. Cisco DNA Center and Juniper Apstra implement this concept. The topology still matters — but you are increasingly describing intent rather than configuring individual devices.
// CHAPTER 11
Choosing the Right Topology — A Decision Framework
Real-world topology decisions are driven by cost, scale, availability requirements, and traffic patterns.
Interactive — Which Topology Should You Use?
Answer three questions and get a topology recommendation.
1. How many devices do you need to connect?
2. How critical is uptime?
3. What is your budget?
The Five Questions to Ask Before Any Topology Decision
// CHAPTER 12
Failure Analysis — What Breaks in Each Topology
The best way to understand a topology is to imagine all the ways it can fail.
Every topology has a characteristic failure mode. Knowing these is essential for both design and troubleshooting.
| Topology | Single Link Fail | Single Node Fail | Multiple Failures | Self-Healing? |
|---|---|---|---|---|
| Bus | 💥 All down | 💥 All down | 💥 All down | ❌ No |
| Star (hub) | ⚡ 1 device | 💥 All down | ⚡ Partial | ❌ No |
| Star (switch) | ⚡ 1 device | 💥 Segment | ⚡ Partial | ⚠️ With redundant switch |
| Ring (single) | 💥 All down | 💥 All down | 💥 All down | ❌ No |
| Ring (dual-SONET) | ✅ No impact | ✅ Wraps in <50ms | ⚡ Depends | ✅ Yes (<50ms) |
| Partial Mesh | ✅ Reroutes | ✅ Reroutes | ⚡ Depends | ✅ Yes (BGP ~minutes) |
| Full Mesh | ✅ Reroutes | ✅ Reroutes | ✅ Very resilient | ✅ Yes |
| Tree (3-tier) | ⚡ Segment | 💥 Zone | ⚡ Partial | ⚠️ With redundant core |
| Leaf-Spine | ✅ ECMP reroutes | ⚡ Partial BW loss | ⚡ Depends | ✅ Yes (ECMP) |
The pattern is clear: resilience requires redundant paths, and redundant paths require mesh characteristics — either a partial mesh between critical nodes, or a redundant star where two switches both connect to all devices. The most cost-effective approach for most enterprise networks is redundant star topology — two switches in every critical position, connected to each other, with devices dual-homed where necessary.
// CHAPTER 13
Common Misconceptions That Will Get You in Trouble
These are the assumptions that cause real outages, failed interviews, and poorly designed networks.
✗ Common Mistake — A hub and a switch are the same thing
✗ Common Mistake — Star topology has no single point of failure
✗ Common Mistake — LAN is always faster than WAN
✗ Common Mistake — Ring topology is completely dead
✗ Common Mistake — Mesh topology means every device connects to every other device
✗ Common Mistake — Three-tier network design is always the right answer for enterprise
// CHAPTER 14
Interview Questions — Test Your Understanding
From entry-level definitions to senior architecture discussions.
What is the difference between LAN, WAN, and MAN?
Why is star topology preferred over bus topology?
What is Spanning Tree Protocol and why is it needed?
When would you choose mesh topology over tree topology?
Explain spine-leaf topology and why it replaced the three-tier model in data centers.
How does the internet's mesh topology relate to BGP's path vector algorithm, and what are the implications for routing policy?
🎯 Key Takeaways
- ✓Network type (LAN/WAN/MAN/PAN/SAN) describes geographic scope and ownership. LAN = one location, high speed, you own it. WAN = multi-city or global, you pay someone else for it.
- ✓Physical topology (Bus/Star/Ring/Mesh/Tree) describes wiring shape and determines resilience, cost, and scale. These are independent axes — a WAN can use ring topology internally.
- ✓Bus topology is dead for LANs — one cable break kills everyone. It survives only in embedded/industrial contexts (CAN bus in cars).
- ✓Star topology (with switches) dominates because each device has dedicated bandwidth, failures are isolated, and it is easy to manage. Switches forward only to the correct port using MAC address tables.
- ✓STP prevents broadcast storms in redundant star topologies by blocking redundant links. RSTP converges in ~1 second. Modern designs avoid STP via routing or port-channel aggregation.
- ✓Mesh topology (full or partial) provides the highest resilience — multiple paths mean routing around failures. The internet is a global partial mesh. Data center spine-leaf is a structured partial mesh.
- ✓Three-tier (core/distribution/access) is the enterprise LAN standard for north-south traffic. Leaf-spine is the data center standard for east-west traffic — always exactly 2 hops, always ECMP load balanced.
- ✓Real networks are always hybrid — star within buildings, tree across floors, partial mesh between buildings, ring or mesh for backbone, VPC/SD-WAN for cloud connectivity.
Quick check
Which topology connects every device to a central switch?
HELP US IMPROVE
How was this lesson?
Your note is shared with the Chaduvuko team for review. Please don’t include personal or sensitive information.
Spotted a mistake or something unclear? Suggest a fix on GitHub or email us. Select the text first and it is quoted for you.
Discussion
0Have a better approach? Found something outdated? Share it — your knowledge helps everyone learning here.