6 Network Topologies: Basic Types
6.2 Learning Objectives
By the end of this section, you will be able to:
- Define Network Topology: Explain what network topology means and why it determines system performance
- Identify the Four Fundamental Topologies: Recognize and diagram star, bus, ring, and mesh configurations
- Compare Topology Trade-offs: Evaluate fault tolerance, cost, and scalability differences across topology types
- Interpret Network Diagrams: Decode topology symbols and connection conventions in technical documentation
- Select Appropriate Topology: Justify topology choices based on specific IoT deployment requirements
For Beginners: Basic Network Topologies
A network topology is the pattern of how devices are connected. In a star topology, everything connects to one central hub (like spokes on a wheel). In a mesh, devices connect to many neighbors (like a fishing net). Each pattern has trade-offs in cost, reliability, and range – and understanding these basics is the first step to designing IoT networks.
Sensor Squad: The Four Network Shapes!
“There are four basic ways to connect IoT devices,” said Max the Microcontroller, drawing on a whiteboard. “Star: everyone connects to one central hub. Simple and cheap, but if the hub dies, EVERYTHING goes down.”
“Bus: everyone shares one long cable,” continued Sammy the Sensor. “Really cheap – just one wire! But if two devices talk at the same time, their messages collide. And if the cable breaks, the whole network splits.”
Lila the LED drew a circle. “Ring: data flows around in a loop, passing from device to device. Everyone gets a fair turn, but one broken device breaks the whole circle. That is why rings are rare in IoT.”
“Mesh is my favorite,” said Bella the Battery. “Devices connect directly to multiple neighbors. If one path fails, data routes around the failure. Zigbee and Thread use mesh topologies for exactly this reason – self-healing networks! The trade-off is cost and complexity. Most real IoT deployments use either star (Wi-Fi, LoRaWAN) or mesh (Zigbee, Thread). Pick star for simplicity and mesh for resilience.”
Related Chapters
Deep Dives:
- Network Topologies Overview - Chapter index and navigation
- Topology Analysis - Graph theory and failure analysis
- Communication Patterns - Data flow patterns
- Hybrid Design - Real-world hybrid topologies
Routing:
- Routing Fundamentals - How routing works in topologies
IoT Protocols:
- Zigbee Mesh - Mesh topology implementation
- LoRaWAN - Star topology for wide area
6.3 Prerequisites
Before diving into this chapter, you should be familiar with:
- Networking Basics: Understanding fundamental networking concepts including switches, routers, hubs, and basic network design principles
6.4 What is a Network Topology?
Simple Explanation
Analogy: Network topology is like how desks are arranged in a classroom. You can arrange desks in rows, circles, groups, or a mix. Each arrangement affects how easily students can communicate, who can see whom, and what happens if one desk is removed.
In everyday terms:
- Star = Everyone talks to one central person (like a teacher in the middle)
- Bus = Everyone sits along one hallway and passes messages down the line
- Ring = Everyone sits in a circle, messages go around
- Mesh = Everyone can talk directly to everyone else
Why Network Topologies Matter for IoT
Understanding network topologies is essential for designing scalable IoT systems. Whether deploying smart home sensors, industrial monitoring, or smart city infrastructure, the topology determines reliability, scalability, and performance. Physical placement of sensors and logical communication patterns directly impact system effectiveness.
Key Takeaway
In one sentence: Your network topology determines fault tolerance, latency, and scalability—star is simple but has a single point of failure, mesh is resilient but complex.
Remember this: Start with star topology for simple deployments (easy to manage), but plan for mesh when reliability matters more than simplicity—a failed hub in star topology takes down everything.
6.5 The Four Fundamental Topologies
6.5.1 Star Topology
In a star topology, all devices connect to a central hub or switch. All communication passes through this central point.
Characteristics:
- Structure: Central hub with radial connections to all devices
- Connections: n-1 connections for n devices
- Path Length: Maximum 2 hops (device → hub → device)
- Management: Easy to add/remove devices without affecting others
Advantages:
- Simple to install and manage
- Easy troubleshooting (isolate faulty device)
- Adding devices doesn’t affect existing connections
- High bandwidth per connection (dedicated link to hub)
Disadvantages:
- Single point of failure at the hub
- Hub bandwidth can become bottleneck
- More cabling required than bus topology
- Hub failure disconnects all devices
IoT Examples: Wi-Fi networks (devices → access point), LoRaWAN (sensors → gateway)
6.5.2 Bus Topology
In a bus topology, all devices connect to a single shared communication line (backbone).
Characteristics:
- Structure: Linear backbone with device taps
- Connections: Single shared medium
- Path Length: Direct access to backbone
- Medium Access: Contention-based (CSMA/CD or similar)
Advantages:
- Simple and inexpensive to implement
- Minimal cabling required
- Easy to extend by adding devices
- Works well for small networks
Disadvantages:
- Single cable failure disconnects all devices
- Collisions reduce performance as devices increase
- Difficult to troubleshoot
- Limited scalability
IoT Examples: Industrial fieldbus (CAN, Modbus), legacy coaxial Ethernet
6.5.3 Ring Topology
In a ring topology, devices connect in a circular chain where data travels in one direction (or both in dual-ring).
Characteristics:
- Structure: Circular chain of devices
- Connections: n connections for n devices
- Path Length: Average (n-1)/2 hops (maximum n-1 hops for unidirectional ring)
- Medium Access: Token passing (deterministic)
Advantages:
- Deterministic latency (predictable timing)
- No collisions (token-based access)
- Equal access for all devices
- Performs well under heavy load
Disadvantages:
- Single break disrupts entire network
- Adding/removing devices interrupts network
- Requires careful configuration
- Higher latency for distant nodes
IoT Examples: Industrial control systems (PROFINET, BACnet MS/TP), FDDI networks
6.5.4 Mesh Topology
In a mesh topology, devices have multiple connections to other devices, providing redundant paths.
Characteristics:
- Full Mesh: Every device connects to every other device (n(n-1)/2 connections)
- Partial Mesh: Selected redundant connections (compromise)
- Path Length: Typically 1-4 hops
- Self-Healing: Routes around failures automatically
Putting Numbers to It
The connection count formula shows why full mesh becomes impractical quickly.
\[L_{full} = \frac{n(n-1)}{2}\]
For example, with 50 nodes: \[L_{full} = \frac{50 \times 49}{2} = 1{,}225 \text{ connections}\]
This means 1,225 physical links or radio connections to maintain! In contrast, partial mesh with each node connecting to just 4 neighbors requires only: \[L_{partial} = \frac{n \times k}{2} = \frac{50 \times 4}{2} = 100 \text{ connections}\]
That is a 92% reduction (100 vs 1,225) while still providing fault tolerance. This is why real IoT mesh networks like Zigbee use partial mesh, not full mesh.
Advantages:
- Highly fault-tolerant (multiple paths)
- Self-healing when nodes fail
- Scales well for coverage area
- No single point of failure
Disadvantages:
- Complex routing and configuration
- Higher cost (more connections)
- Routing overhead consumes bandwidth
- More difficult to manage
IoT Examples: Zigbee mesh, Thread/Matter, BLE Mesh, Z-Wave
6.6 Topology Comparison
| Topology | Connections (n nodes) | Max Hops | Fault Tolerance | Complexity | Best For |
|---|---|---|---|---|---|
| Star | n - 1 | 2 | Low (SPOF) | Low | Simple deployments |
| Bus | 1 backbone | 1 | Low (SPOF) | Low | Small networks |
| Ring | n | n-1 | Medium | Medium | Deterministic timing |
| Mesh | n(n-1)/2 (full) | 1 | High | High | Critical systems |
6.7 Worked Example: Calculating Connection Cost by Topology
Worked Example: Wiring Budget for a 20-Node Warehouse Network
Scenario: A logistics warehouse needs to connect 20 barcode scanners on the pick-and-pack floor. Each wired connection costs $150 (cable, termination, and labor). The operations manager wants to understand how topology choice affects the wiring budget.
Given:
- n = 20 nodes
- Cost per connection = $150
- Requirement: at least one redundant path per node
Step 1: Calculate connections for each topology
| Topology | Formula | Connections | Cable Cost |
|---|---|---|---|
| Star | n - 1 | 19 | $2,850 |
| Bus | 1 backbone | 1 run + 20 taps | ~$800 |
| Ring | n | 20 | $3,000 |
| Full Mesh | n(n-1)/2 | 190 | $28,500 |
| Partial Mesh (k=3) | n x k / 2 | 30 | $4,500 |
Step 2: Evaluate fault tolerance
- Star (19 connections): Zero redundancy. Hub failure disconnects all 20 scanners. Adding a backup hub costs $500 + 19 cables = $3,350.
- Ring (20 connections): A single ring is unidirectional – one cable break isolates all devices downstream of the break. Dual-ring (e.g., FDDI) provides a backup path in the reverse direction, but requires double the cabling.
- Partial Mesh k=3 (30 connections): Each scanner connects to 3 neighbors. One failure per node is tolerated. Two simultaneous failures may still isolate a scanner.
- Full Mesh (190 connections): Maximum redundancy – any 18 simultaneous failures still leave every scanner connected. But at 10x the cost of star.
Step 3: Decision
The warehouse chooses star with backup hub ($3,350) because:
- Scanners are stationary (no mesh routing benefit)
- A single hub serves the entire floor (small physical area)
- Backup hub provides redundancy at 17% of full-mesh cost
- Simpler troubleshooting when a scanner fails
Key Insight: Full mesh is rarely justified for small, localized deployments. The connection count grows quadratically (n^2), making it prohibitively expensive above ~30 nodes. Partial mesh or dual-star configurations offer the best cost-to-redundancy ratio for most IoT scenarios.
6.8 Topology Selection Decision Tree
Alternative View: Topology Selection Decision Tree
This decision tree helps select the optimal network topology based on IoT deployment requirements.
6.9 Visual Reference: Logical vs Physical Topologies
Alternative Views: Network Topology Visualizations
The star topology is the most common in modern networks, including home Wi-Fi and enterprise Ethernet. All traffic flows through the central hub, making it easy to manage and troubleshoot but creating a single point of failure if the hub fails.
Star topology is common in LPWAN protocols like LoRaWAN and Sigfox, where battery-powered sensors communicate directly with a gateway. This minimizes power consumption since devices don’t need to route traffic for other devices.
Choosing between star and mesh depends on requirements. Star offers simplicity and low latency (single hop) but limited range and single point of failure. Mesh provides extended range and redundancy through multi-hop routing but adds complexity and latency.
Tree (hierarchical) topology combines star topologies in a parent-child structure. Common in campus networks and Zigbee cluster-tree deployments, it provides scalable organization but relies on parent nodes being available.
Tree topology is natural for building automation where floor controllers connect to wing controllers, which connect to room sensors. The hierarchy matches the physical building structure and simplifies addressing schemes.
6.10 Understanding Check: Smart Building Network Design
Understanding Check: Smart Building Network Design
Scenario: You’re designing networking for a 50,000 sq ft office building with 200 IoT devices: 120 LED lights, 40 HVAC sensors, 20 security cameras, 20 door locks. Requirements: lights must stay functional even if one fails, cameras need high bandwidth (2 Mbps each), HVAC sensors need ultra-reliability, door locks need redundant paths for safety. Budget: $80K for networking infrastructure.
Think about:
- Would you use the same topology for all four device types? Why or why not?
- What happens if your central switch fails in a star topology?
Key Insight: Use hybrid topology: Mesh for lights (Zigbee mesh, $10/device, survives individual node failure), Star for cameras (PoE switch, $3K, high bandwidth), Ring for HVAC (BACnet MS/TP, $500, deterministic token-passing), Dual-star for locks (two star controllers, $8K, failover).
Cost breakdown: - Lights: 120 x $10 Zigbee modules = $1,200 (mesh self-heals when fixtures fail) - Cameras: 20 x $200 PoE cameras + $3,000 switch (20 cameras × 2 Mbps = 40 Mbps total, well below 1 Gbps switch capacity) = $7,000 - HVAC: 40 x $50 sensors + $500 BACnet controller = $2,500 (BACnet MS/TP ring gives deterministic token-passing access) - Locks: 20 x $300 locks + 2 x $4,000 controllers (primary + backup) = $14,000 - Total: $24,700 vs $120K for full mesh or single-point-of-failure star
Hybrid reasoning: Lights tolerate delay (mesh routing latency OK), cameras need bandwidth (star provides direct paths), HVAC needs reliability (BACnet MS/TP ring with token-passing gives deterministic, collision-free access), locks need failover (dual controllers eliminate single point of failure).
Verify Your Understanding:
- Why would a pure mesh topology fail for 20x 2Mbps camera streams? (Hint: multi-hop routing adds latency and each relay hop consumes bandwidth.)
- Why is ring topology chosen for HVAC sensors here even though a single break disrupts the ring? (Hint: consider the physical environment and what BACnet MS/TP token-passing offers that Wi-Fi does not.)
Common Pitfalls
1. Assuming Star Topology Is Always the Simplest Choice
Star is simple to install but the hub becomes a bottleneck at high node counts and a SPOF that takes down all connected devices. Fix: add a backup hub for any deployment where hub failure is unacceptable.
2. Selecting Mesh Because It Sounds More Resilient Without Checking Cost
Full mesh of 50 nodes requires 1,225 connections vs 49 for star. The cost and complexity is prohibitive for most IoT budgets. Fix: use partial mesh (each node connects to 2–4 neighbours) for a 90%+ reduction in connections while retaining self-healing capability.
3. Using Ring Topology in Environments Where Node Failure Is Common
A single failed ring node breaks the loop and isolates all downstream devices. Fix: use ring only where nodes are highly reliable and maintenance access is easy, or deploy dual-ring for automatic failover.
4. Treating Topology as Fixed After Deployment
IoT networks grow and contract over time. A star that fits 20 nodes will bottleneck at 200. Fix: design the initial topology with a planned upgrade path, such as switching from star to tree-star when node count exceeds 50.
6.11 Summary
Network topologies define how IoT devices are interconnected. The four fundamental topologies each have distinct characteristics:
Star Topology:
- Central hub with radial connections
- Easy management, single point of failure
- Best for: Simple deployments, high-bandwidth devices (Wi-Fi cameras)
Bus Topology:
- Shared backbone, all devices tap in
- Simple and inexpensive, limited scalability
- Best for: Small networks, industrial fieldbus
Ring Topology:
- Circular chain, token-based access
- Deterministic timing, single break disrupts network
- Best for: Industrial control systems requiring predictable latency
Mesh Topology:
- Multiple redundant paths between devices
- Self-healing, complex routing
- Best for: Critical systems, large coverage areas (Zigbee, Thread)
Key Design Principle: Real-world IoT deployments rarely use pure topologies. Hybrid designs combine multiple topology types to optimize for different requirements across device classes.
6.12 Knowledge Check
6.13 What’s Next
| Direction | Chapter | Focus |
|---|---|---|
| Next | Topology Analysis | Graph theory, failure analysis, routing overhead |
| Previous | Core Concepts | Physical vs logical topology fundamentals |
| Related | Communication Patterns | Unicast, multicast, many-to-one data flows |