12 Topology Selection

Key Concepts

Topology Selection: The process of choosing the network arrangement that best satisfies a deployment’s requirements for cost, reliability, scalability, and latency
Decision Tree: A branching diagram that guides topology selection based on answers to yes/no requirement questions
Requirement Priority: Ranking requirements by importance so that when trade-offs arise, the higher-priority requirement is preserved
Deployment Classification: Categorising a deployment as small-scale, medium-scale, or large-scale to narrow the viable topology options
Environment Factor: Physical and RF environment characteristics (indoor, outdoor, industrial, residential) that constrain radio range and link reliability
Lifecycle Consideration: How long the deployment must run and how topology choice affects maintainability and upgrade cost over that period
Selection Confidence: A measure of how certain the designer is that the chosen topology will meet requirements; increases with pilot testing

12.1 In 60 Seconds

Selecting the right IoT network topology requires balancing range, latency, bandwidth, device count, and power consumption against cost. Star (Wi-Fi) supports 50-250 devices at 10-50ms latency, mesh (Zigbee) scales to 65,000 devices with self-healing, LoRaWAN star reaches 5-15 km at 10 mA per device, and hierarchical tree offers unlimited scaling via wired backbone tiers. Use the decision framework in this chapter to match your requirements to the optimal topology.

12.2 Learning Objectives

By the end of this section, you will be able to:

Apply Decision Frameworks: Use structured criteria and decision matrices to select the optimal topology
Compare Performance Metrics: Quantify latency, bandwidth, and scalability trade-offs across topology types
Estimate Deployment Costs: Calculate infrastructure and per-device costs for star, mesh, and tree options
Defend Topology-Application Matches: Justify why a specific topology best serves a given IoT use case

For Beginners: Choosing a Topology

Picking the right network topology is like choosing the right layout for a new office building. Do you want everyone in one big open room (bus), separate offices connected to a hallway (star), or lots of interconnected meeting rooms (mesh)? Each layout has pros and cons depending on how many people need to communicate and how important reliability is.

Sensor Squad: Picking the Perfect Topology!

“Which topology should we use?” asked Sammy the Sensor. Max the Microcontroller pulled out a decision framework. “It depends on your specific requirements. How many devices? What range? What latency? What is your power budget?”

“If you have fewer than 250 devices within Wi-Fi range and need low latency, a star topology works great,” Max explained. “If you need self-healing and can tolerate some extra latency, mesh is your answer – Zigbee meshes can scale to 65,000 devices!”

“For long-range deployments like a city-wide sensor network,” added Lila the LED, “LoRaWAN uses a star topology that reaches 5-15 kilometers per device. And if you need unlimited scaling, a hierarchical tree with a wired backbone can support millions of devices across multiple sites.”

Bella the Battery put it simply. “Star is cheap and simple but has a single point of failure. Mesh is resilient but complex and uses more energy for routing. Tree scales well but needs careful planning. Use the decision matrix in this chapter – plug in your numbers and the right topology becomes obvious!”

12.3 Prerequisites

Topologies Introduction: Physical vs logical topology concepts
Topology Types: Understanding of star, mesh, ring, bus, tree characteristics

12.4 Topology Decision Framework with Specific Numbers

IoT Topology Selection Matrix

Use this framework to choose the right topology for your IoT deployment based on quantified requirements.

12.4.1 Performance Comparison Table

Metric	Star (Wi-Fi)	Mesh (Zigbee)	Star (LoRaWAN)	Tree (Hierarchical)
Max Range	100m	10m per hop, extends with hops	5-15 km	Varies (wired backbone unlimited)
Typical Latency	10-50ms	50-200ms (multi-hop)	1-10 seconds	1-100ms (depends on tiers)
Bandwidth	50-600 Mbps	250 kbps	0.3-50 kbps	1 Gbps+ (wired tiers)
Devices Supported	50-250	65,000	1,000 per gateway	Unlimited (hierarchical scaling)
Power (Avg Device)	500 mA	15 mA	10 mA	Varies (usually powered)
Cost per Node	$20-50	$5-15	$10-30	$50-200 (includes switch/gateway)
Failure Tolerance	0% (hub fails = all down)	30-40% node loss	0% (gateway down)	Gateway redundancy available
Setup Complexity	Low (1-2 hours)	Medium (4-8 hours)	Low (2-4 hours)	High (days to weeks)

12.4.2 Decision Flowchart

The following flowchart illustrates the branching decision logic used when assigning roles during network provisioning — a pattern applicable to mesh topology node role assignment (router vs end-device vs coordinator):

Decision flowchart showing branching logic to select between Relay, Proxy, and Provisioner roles based on device capabilities in a network deployment

12.5 Use Star Topology When…

Choose Star if 3+ of these apply:

Small deployment (<50 devices)
Good line-of-sight to central location
High bandwidth needed (>1 Mbps per device)
Simple setup is priority (install in <2 hours)
AC power available at central hub
Budget < $50/device
Downtime acceptable (99% uptime OK)

Real-world examples:

Home automation: 15 devices, Wi-Fi router hub, $30/device
Office conference rooms: 10 sensors per room, PoE switch hub
Parking lot: LoRaWAN gateway covers 500 spaces, 5 km range

Cost breakdown (50-device star):

Hub/Gateway:        $200-500
Devices (50 × $30): $1,500
Installation:       $500
Total:              $2,200-2,500 ($44-50/device)

12.6 Use Mesh Topology When…

Choose Mesh if 3+ of these apply:

High reliability required (>99.9% uptime)
Physical obstacles (walls, metal equipment)
Large deployment (>50 devices)
Battery-powered sensors
Expansion expected (easy to add nodes)
Self-healing critical (remote/unmanned location)
Low data rate acceptable (<250 kbps)

Real-world examples:

Smart building: 200 sensors, Zigbee mesh, batteries last 3-5 years
Industrial monitoring: 500 nodes, Thread mesh, survives 40% node failure
Smart agriculture: 100 soil sensors, mesh extends range across farm

Putting Numbers to It

Let’s calculate the per-device cost for a mesh topology deployment with different node ratios.

Given: Total devices $N = 200$, coordinator $C = 1$, router percentage $p_r = 0.10$ (10% are powered routers)

Component costs: \[N_{\text{routers}} = \lfloor N \times p_r \rfloor = \lfloor 200 \times 0.10 \rfloor = 20\] \[N_{\text{end}} = N - N_{\text{routers}} - C = 200 - 20 - 1 = 179\]

Total cost: \[\text{Cost}_{\text{total}} = C_{\text{coord}} + N_r \times C_r + N_e \times C_e + C_{\text{install}}\] \[= \$100 + 20 \times \$15 + 179 \times \$10 + \$1{,}000 = \$3{,}390\]

Cost per device: \[\text{Cost}_{\text{per-device}} = \frac{\$3{,}390}{200} = \$16.95 \approx \$17\]

Scalability: If router ratio drops to $p_r = 0.05$ (5%), total cost $= \$100 + 10(\$15) + 189(\$10) + \$1{,}000 = \$3{,}140$ or $\$15.70$/device. Optimal router ratio balances relay capacity vs cost.

Cost breakdown (200-device mesh):

Coordinator/Hub:          $100
Router nodes (20 × $15):  $300  (Powered devices that relay)
End devices (179 × $10):  $1,790 (Battery sensors)
Installation:             $1,000
Total:                    $3,190 ($15.95/device ≈ $16/device)

Try It: Mesh Deployment Cost Calculator

Show code

viewof meshDevices = Inputs.range([10, 500], {label: "Total devices (N)", step: 10, value: 200})
viewof routerPct = Inputs.range([2, 30], {label: "Router percentage (%)", step: 1, value: 10})
viewof coordCost = Inputs.range([50, 500], {label: "Coordinator cost ($)", step: 10, value: 100})
viewof routerCost = Inputs.range([5, 100], {label: "Router node cost ($)", step: 5, value: 15})
viewof endCost = Inputs.range([5, 100], {label: "End device cost ($)", step: 5, value: 10})
viewof installCost = Inputs.range([0, 5000], {label: "Installation cost ($)", step: 100, value: 1000})

Show code

{
  const nRouters = Math.floor(meshDevices * routerPct / 100)
  const nEnd = meshDevices - nRouters - 1
  const total = coordCost + nRouters * routerCost + nEnd * endCost + installCost
  const perDevice = (total / meshDevices).toFixed(2)

  return html`
    <div style="background:#f0f7f4;border-left:4px solid #16A085;padding:14px 18px;border-radius:4px;font-family:Arial,sans-serif;">
      <strong style="color:#2C3E50;font-size:14px;">Mesh Cost Breakdown</strong>
      <table style="width:100%;margin-top:10px;border-collapse:collapse;font-size:13px;">
        <tr style="background:#16A085;color:white;">
          <th style="padding:6px 10px;text-align:left;">Component</th>
          <th style="padding:6px 10px;text-align:right;">Count</th>
          <th style="padding:6px 10px;text-align:right;">Unit Cost</th>
          <th style="padding:6px 10px;text-align:right;">Total</th>
        </tr>
        <tr style="background:white;">
          <td style="padding:5px 10px;">Coordinator</td>
          <td style="padding:5px 10px;text-align:right;">1</td>
          <td style="padding:5px 10px;text-align:right;">$${coordCost}</td>
          <td style="padding:5px 10px;text-align:right;">$${coordCost}</td>
        </tr>
        <tr style="background:#f8f8f8;">
          <td style="padding:5px 10px;">Router nodes</td>
          <td style="padding:5px 10px;text-align:right;">${nRouters}</td>
          <td style="padding:5px 10px;text-align:right;">$${routerCost}</td>
          <td style="padding:5px 10px;text-align:right;">$${nRouters * routerCost}</td>
        </tr>
        <tr style="background:white;">
          <td style="padding:5px 10px;">End devices</td>
          <td style="padding:5px 10px;text-align:right;">${nEnd}</td>
          <td style="padding:5px 10px;text-align:right;">$${endCost}</td>
          <td style="padding:5px 10px;text-align:right;">$${nEnd * endCost}</td>
        </tr>
        <tr style="background:#f8f8f8;">
          <td style="padding:5px 10px;">Installation</td>
          <td style="padding:5px 10px;text-align:right;">—</td>
          <td style="padding:5px 10px;text-align:right;">—</td>
          <td style="padding:5px 10px;text-align:right;">$${installCost}</td>
        </tr>
        <tr style="background:#2C3E50;color:white;font-weight:bold;">
          <td style="padding:6px 10px;">Total (${meshDevices} devices)</td>
          <td colspan="2" style="padding:6px 10px;text-align:right;">Per device:</td>
          <td style="padding:6px 10px;text-align:right;">$${total} ($${perDevice}/device)</td>
        </tr>
      </table>
    </div>
  `
}

12.7 Use Tree (Hierarchical) Topology When…

Choose Tree if 3+ of these apply:

Very large deployment (>1,000 devices)
Multi-building campus or city
Mix of wired and wireless
Tiered data processing (edge/fog/cloud)
Departmental/geographic organization
High-speed backbone needed
Professional IT infrastructure available

Real-world examples:

University campus: Fiber backbone, Wi-Fi per building, sensors per floor
Smart city: Fiber to neighborhoods, LoRa gateways, streetlight sensors
Factory complex: Ethernet backbone, wireless mesh per production area

Cost breakdown (2,000-device tree):

Core switches (3 × $5,000):        $15,000
Distribution switches (20 × $500): $10,000
Edge devices (2,000 × $20):        $40,000
Fiber installation:                $30,000
Total:                             $95,000 ($47.50/device)

12.8 Specific Numbers for Common IoT Applications

Application	Recommended Topology	Typical Scale	Cost/Device	Battery Life	Key Metric
Smart Home	Star (Wi-Fi)	10-30 devices	$30	N/A (powered)	Simplicity
Building Automation	Mesh (Zigbee)	100-500 devices	$15	3-5 years	Reliability 99.9%
Smart City Lights	Star (LoRaWAN)	1,000-50,000	$25	5-10 years	Range 5-15 km
Industrial Monitoring	Mesh (Thread)	200-2,000	$20	2-4 years	Uptime 99.99%
Campus Network	Tree (Hybrid)	5,000-50,000	$50	N/A (powered)	Scalability
Agriculture	Star (LoRaWAN) + Mesh	50-500	$35	2-5 years	Coverage 10+ km
Healthcare	Tree (Wired + Wi-Fi)	500-5,000	$75	N/A (critical)	Latency <100ms
Retail Stores	Mesh (BLE)	50-200	$10	1-2 years	Cost <$15/device

12.9 Bandwidth vs Range Trade-offs

The Fundamental IoT Triangle - You Can Pick Two:

The IoT design triangle captures the core constraint: optimizing simultaneously for range, bandwidth, and low power is impossible. Every technology and topology requires a trade-off among these three dimensions.

Six-step process diagram showing a sequential workflow across two rows, with numbered steps connected by arrows illustrating a staged decision or configuration process

Key takeaway: No topology is perfect. Choose based on your top 2 priorities, accept the limitation on the 3rd.

12.9.1 Technology Range-Power Comparison

The key principle for selecting IoT communication technology is matching range and power budget to deployment requirements:

Four-step sequential process diagram showing stages: calculate hash of next stage, compare with stored reference, proceed if match, halt boot if mismatch — illustrating a layered verification workflow

Range-Power Trade-offs by Technology:

LoRaWAN: Wide-area (5-15 km), ultra-low power (10-50 µA average) — ideal for battery-powered remote sensors
BLE / Zigbee / Thread: Short-range (10-100 m), low power (15 mA active) — best for indoor mesh deployments
Wi-Fi: Medium-range (50-100 m), higher power (500 mA active) — suits high-bandwidth, AC-powered devices
Cellular (LTE-M / NB-IoT): Wide-area, moderate power — for devices requiring mobile connectivity

Topology Implications:

Star topologies work best with technologies at bandwidth extremes (Wi-Fi or LoRaWAN)
Mesh topologies extend the effective range of short-range low-power technologies (Zigbee, Thread, BLE)
Hybrid topologies combine technologies from different range-power categories to meet mixed requirements

12.10 Understanding Checks: Real IoT Scenarios

Understanding Check: Smart Factory Deployment

Scenario: You’re deploying 500 sensors across a 200,000 sq ft manufacturing facility. The factory has: - Heavy machinery causing RF interference - Metal walls and equipment blocking signals - Critical safety requirements (99.9% uptime needed) - 24/7 operations with $50,000/hour downtime cost

Think about: Why would you choose mesh topology over star for this deployment?

Key Insights:

Self-Healing = Uptime: Mesh networks automatically route around failed nodes
- Star topology: Hub failure = 100% network down = $50,000/hour loss
- Mesh topology: Can survive 30-40% node failures with no downtime
- Real number: Zigbee mesh maintains connectivity even if 100 out of 500 sensors fail
RF Penetration: Metal obstacles block Wi-Fi signals
- Star (Wi-Fi): Direct line-of-sight to hub required, dead zones behind metal equipment
- Mesh (Zigbee/Thread): Messages hop around obstacles through neighboring sensors
- Real number: Mesh reduces “dead zones” by 90% compared to star in industrial environments
Scalability: 500 sensors overwhelm single hub
- Star (Wi-Fi): Single access point supports ~50 devices before congestion
- Mesh (Zigbee): Each router node extends capacity, supports 65,000 nodes/network
- Real number: Mesh handles 10x more devices per area than star

Decision Rule:

Use MESH when:
- Reliability > 99% required
- Physical obstacles (metal, concrete)
- Large number of devices (>50)
- Long-term deployment (installation cost amortized)

Use STAR when:
- Simple setup is priority
- Open space with good line-of-sight
- Small number of devices (<20)
- Temporary deployment

Understanding Check: Smart City Streetlights

Scenario: A city wants to network 10,000 streetlights across 50 square miles for: - Remote on/off control - Energy monitoring - Maintenance alerts (bulb failures) - Budget: $2M for networking equipment

Think about: Why would LoRaWAN star topology beat Wi-Fi mesh for this application?

Key Insights:

Range vs Density Trade-off:
- Wi-Fi mesh: 100m range → Need 10,000 devices as routers → Expensive
- LoRaWAN star: 5-15 km range → Need only 10-20 gateways → Cost-effective
- Real numbers: LoRaWAN gateway covers 500 streetlights, Wi-Fi AP covers 5-10
Bandwidth Requirements:
- Streetlight data: ~100 bytes/minute (on/off status, power consumption)
- LoRaWAN: 50 kbps sufficient for this low-bandwidth application
- Wi-Fi: Overkill — paying for 100+ Mbps when 100 bytes/minute is all that is needed
- Real number: LoRaWAN costs $50/device, Wi-Fi mesh costs $200/device
Power Consumption:
- Streetlights already have power, but reducing consumption saves money
- LoRaWAN: 10-50 mA average → $2/year electricity per device
- Wi-Fi: 500-1000 mA average → $20/year electricity per device
- Real numbers: LoRaWAN saves $180,000/year on electricity for 10,000 devices

Decision Rule:

Use STAR (LoRaWAN) when:
- Low data rate (<50 kbps)
- Wide area coverage (>1 km²)
- Battery-powered devices
- Cost-sensitive deployment

Use MESH (Wi-Fi/Zigbee) when:
- High data rate (video, audio)
- Indoor/dense deployment
- Reliability > range
- Power available

Understanding Check: Hospital Patient Monitoring

Scenario: A 500-bed hospital needs real-time patient monitoring: - Heart rate, oxygen, temperature sensors - Patients move between rooms - Life-critical data (missed reading = patient death) - 1-second update rate required

Think about: Why would you use a hybrid topology (wired star backbone + wireless mesh access)?

Key Insights:

Latency Layering:
- Critical path: Sensor → Mesh (Wi-Fi) → Wired Star → Monitoring Station
- Wireless mesh: 10-50ms latency (acceptable for 1-second updates)
- Wired backbone: 1-5ms latency (ensures fast central processing)
- Real number: Hybrid achieves 50-100ms end-to-end vs 200ms pure wireless
Mobility Support:
- Patients move: Room 301 → Radiology → Room 405
- Mesh topology: Seamless handoff between access points
- Star topology alone: Would need AP in every room (expensive)
- Real number: Mesh reduces AP count by 60% while maintaining coverage
Reliability Tiers:
- Wired backbone: 99.999% uptime (fiber optic, redundant paths)
- Wireless mesh: 99.9% uptime (self-healing, but RF interference possible)
- Real number: Hybrid achieves 99.99% uptime (critical for life-safety)

Decision Rule:

Use HYBRID (Wired + Wireless) when:
- Critical reliability AND mobility
- High throughput AND wide coverage
- Tiered latency requirements
- Hospital, industrial, campus networks

Architecture Pattern:
Level 1: Wired fiber backbone (reliability)
Level 2: Wired switch per floor/building (aggregation)
Level 3: Wireless mesh access layer (mobility + coverage)

12.11 Worked Example: Selecting a Topology for a Smart Warehouse

Scenario: A logistics company is equipping a 10,000 m² warehouse with IoT sensors to track inventory (RFID readers at dock doors), monitor environmental conditions (temperature/humidity in cold storage zones), and detect worker safety events (emergency buttons). They need to select a topology.

Given:

30 RFID readers at dock doors and aisles (need 2 Mbps each for real-time inventory scans)
80 temperature/humidity sensors in cold storage (send 50-byte readings every 5 minutes)
20 emergency buttons on worker vests (must deliver alert within 500ms, 99.99% reliable)
Budget: $75,000 for networking infrastructure
Metal shelving racks throughout warehouse (severe RF obstruction)

Step 1: Classify each data flow’s requirements

Device Type	Count	Bandwidth	Latency	Reliability	Power
RFID readers	30	2 Mbps	<100ms	99.9%	AC-powered
Temp/humidity sensors	80	1.3 kbps	Seconds OK	99%	Battery (5 yr target)
Emergency buttons	20	<1 kbps	<500ms	99.99%	Battery (2 yr min)

Step 2: Match each device class to a topology

RFID readers need high bandwidth + AC power available = Star (Wi-Fi) to PoE access points. 30 readers / ~15 per AP = 3 access points needed.
Temp/humidity sensors need low power + metal obstructions = Mesh (Zigbee) to hop around shelving. 80 sensors with 10 AC-powered routers (placed on top of racks) provide k=3 redundancy.
Emergency buttons need ultra-reliable + low latency + mobile workers = Mesh (BLE) piggybacking on Zigbee routers. BLE’s 10ms connection interval meets the 500ms latency budget even with 3 hops.

Step 3: Calculate cost

Component	Quantity	Unit Cost	Total
Wi-Fi APs (enterprise PoE)	3	$800	$2,400
PoE switch (48-port)	1	$1,200	$1,200
RFID readers (Wi-Fi)	30	$450	$13,500
Zigbee coordinator	1	$150	$150
Zigbee routers (AC-powered)	10	$45	$450
Temp/humidity sensors (Zigbee)	80	$25	$2,000
BLE emergency buttons	20	$35	$700
Gateway/server	1	$3,000	$3,000
Installation + cabling	–	–	$5,000
Total			$28,400

Step 4: Verify against requirements

Budget: $28,400 vs $75,000 budget — well within limits (leaves room for redundancy)
RFID bandwidth: 3 APs × 50 Mbps usable = 150 Mbps for 30 readers needing 60 Mbps total — sufficient
Sensor battery life: Zigbee end devices at 1 msg/5 min with 2×AA = ~6 years — exceeds 5-year target
Emergency latency: BLE mesh, 3 hops × 10ms + processing = ~50ms — well under 500ms requirement
Metal obstructions: Zigbee mesh routes around shelving via elevated routers

Conclusion: A hybrid topology (Wi-Fi star for RFID + Zigbee/BLE mesh for sensors/safety) meets all requirements at 38% of budget. The key insight is that different device classes have fundamentally different requirements, and no single topology optimally serves all three. Trying to force everything onto Wi-Fi star would require 30+ access points to overcome metal obstructions ($24,000+ in APs alone) while still failing the 5-year battery requirement for sensors.

12.12 Topology Selection Checklist

Before choosing a topology, ask:

Question	Guides You Toward
How many devices?	<20: Star, 20-100: Mesh, >100: Hierarchical
Battery or powered?	Battery: Mesh (low power), Powered: Star (simplicity)
How critical is uptime?	Mission-critical: Mesh/Dual-ring, Normal: Star
Indoor or outdoor?	Outdoor/large area: Mesh (range), Indoor/small: Star
Do I have skilled staff?	No: Star (simple), Yes: Mesh acceptable
What’s my budget?	Low: Star, Moderate: Partial mesh, High: Full mesh
Bandwidth needs?	High (video): Wi-Fi star, Low (sensors): Zigbee mesh

Golden Rule: Choose the SIMPLEST topology that meets your requirements—complexity is the enemy of reliability!

12.13 How It Works: Topology Selection Process

The topology selection process follows a systematic evaluation framework:

Step 1: Characterize Your Deployment

Device count: <20, 20-100, >100
Power source: Battery (target life?), Mains
Physical environment: Indoor/outdoor, obstacles
Reliability target: 99%, 99.9%, 99.99%

Step 2: Apply Decision Matrix For each criterion, score topologies (0-5): - Star: Simple but single point of failure - Mesh: Resilient but complex - Tree: Scalable but needs planning

Step 3: Calculate Total Cost of Ownership Include capex (devices, installation) and opex (battery replacement, maintenance labor)

Step 4: Validate with Worked Example Use similar deployed systems as reference (smart warehouse, campus network)

12.14 Incremental Example: From 10 to 1,000 Devices

Stage 1: Prototype (10 devices)

Topology: Simple star (single Wi-Fi AP)
Cost: $500 (1 AP + 10 sensors)
Why: Fastest time to market, easy debugging
Limitation: Doesn't scale, no redundancy

Stage 2: Pilot (50 devices)

Topology: Extended star (3 APs, 1 switch)
Cost: $2,500 ($50/device)
Why: Proves scalability pattern
Limitation: Still has central switch as SPOF

Stage 3: Production (500 devices)

Topology: Partial mesh (Zigbee) + wired backbone
Cost: $15,000 ($30/device)
Why: Mesh resilience, lower per-device cost
Key insight: Topology choice changed at scale

Stage 4: Enterprise (1,000+ devices)

Topology: Hierarchical tree (fiber + mesh)
Cost: $50,000 ($50/device, includes infrastructure)
Why: Only architecture that scales to thousands

Lesson: Topology requirements evolve with deployment size. Start simple, plan for scale.

Try It: 5-Year Total Cost of Ownership Calculator

Compare star vs mesh topology costs over a full deployment lifecycle.

Show code

viewof tcoDevices = Inputs.range([10, 1000], {label: "Number of devices", step: 10, value: 100})
viewof starDeviceCost = Inputs.range([5, 200], {label: "Star device cost ($/unit)", step: 5, value: 25})
viewof meshDeviceCost = Inputs.range([5, 200], {label: "Mesh device cost ($/unit)", step: 5, value: 35})
viewof starBatteryYears = Inputs.range([0.5, 5], {label: "Star battery life (years)", step: 0.5, value: 1})
viewof meshBatteryYears = Inputs.range([1, 10], {label: "Mesh battery life (years)", step: 0.5, value: 4})
viewof batteryReplaceCost = Inputs.range([10, 200], {label: "Battery replacement cost ($/event)", step: 5, value: 55})
viewof tcoYears = Inputs.range([1, 10], {label: "Planning horizon (years)", step: 1, value: 5})

Show code

{
  const starCapex = tcoDevices * starDeviceCost
  const meshCapex = tcoDevices * meshDeviceCost

  const starReplacements = Math.floor(tcoYears / starBatteryYears)
  const meshReplacements = Math.floor(tcoYears / meshBatteryYears)

  const starOpex = tcoDevices * starReplacements * batteryReplaceCost
  const meshOpex = tcoDevices * meshReplacements * batteryReplaceCost

  const starTotal = starCapex + starOpex
  const meshTotal = meshCapex + meshOpex
  const saving = starTotal - meshTotal
  const winner = saving > 0 ? "Mesh" : saving < 0 ? "Star" : "Equal"
  const winnerColor = saving > 0 ? "#16A085" : saving < 0 ? "#E74C3C" : "#7F8C8D"
  const savingAbs = Math.abs(saving)
  const pct = starTotal > 0 ? ((savingAbs / Math.max(starTotal, meshTotal)) * 100).toFixed(1) : 0

  return html`
    <div style="background:#f4f8fb;border-left:4px solid #3498DB;padding:14px 18px;border-radius:4px;font-family:Arial,sans-serif;">
      <strong style="color:#2C3E50;font-size:14px;">5-Year TCO Comparison (${tcoDevices} devices, ${tcoYears}-year horizon)</strong>
      <table style="width:100%;margin-top:10px;border-collapse:collapse;font-size:13px;">
        <tr style="background:#3498DB;color:white;">
          <th style="padding:6px 10px;text-align:left;">Cost Item</th>
          <th style="padding:6px 10px;text-align:right;">Star Topology</th>
          <th style="padding:6px 10px;text-align:right;">Mesh Topology</th>
        </tr>
        <tr style="background:white;">
          <td style="padding:5px 10px;">Device capex</td>
          <td style="padding:5px 10px;text-align:right;">$${starCapex.toLocaleString()}</td>
          <td style="padding:5px 10px;text-align:right;">$${meshCapex.toLocaleString()}</td>
        </tr>
        <tr style="background:#f8f8f8;">
          <td style="padding:5px 10px;">Battery replacements (${starReplacements}× star / ${meshReplacements}× mesh)</td>
          <td style="padding:5px 10px;text-align:right;">$${starOpex.toLocaleString()}</td>
          <td style="padding:5px 10px;text-align:right;">$${meshOpex.toLocaleString()}</td>
        </tr>
        <tr style="background:#2C3E50;color:white;font-weight:bold;">
          <td style="padding:6px 10px;">Total ${tcoYears}-year cost</td>
          <td style="padding:6px 10px;text-align:right;">$${starTotal.toLocaleString()}</td>
          <td style="padding:6px 10px;text-align:right;">$${meshTotal.toLocaleString()}</td>
        </tr>
      </table>
      <div style="margin-top:12px;padding:10px 14px;background:white;border-radius:4px;border:1px solid #ddd;">
        <strong style="color:${winnerColor};font-size:15px;">${winner} saves $${savingAbs.toLocaleString()} (${pct}%) over ${tcoYears} years</strong>
        <br/><span style="color:#7F8C8D;font-size:12px;">Key driver: battery replacement labor cost of $${batteryReplaceCost}/event at scale dominates initial device price difference.</span>
      </div>
    </div>
  `
}

12.15 Concept Check: When Does Mesh Win Over Star?

## Concept Relationships {#topo-selection-relationships}

Topology selection integrates multiple networking concepts:

Performance Metrics:

Latency vs Range Trade-off - Star has lower latency, mesh extends range
Bandwidth Scaling - Tree provides aggregation points
Fault Tolerance Levels - Mesh > Tree > Star > Bus

Cost Factors:

Capex: Device hardware, installation labor
Opex: Battery replacement, field service, troubleshooting time
Opportunity cost: Downtime cost for mission-critical systems

Technology Integration:

Wi-Fi Star Topology - 50-250 devices per AP
Zigbee Mesh - Up to 65,000 devices, self-healing
LoRaWAN Star - 5-15 km range, 1,000+ devices per gateway

Decision Frameworks:

IoT Triangle (range, bandwidth, power) - Can optimize for only 2 of 3
Reliability Budget - Convert uptime requirement to topology constraint
Total Cost of Ownership - Include 5-year opex, not just capex

12.16 See Also

Related Topology Chapters:

Topology Types - Detailed characteristics of each topology
Topology Failures - What happens when things break
Topology Review - Comprehensive comparison tables

Protocol Integration:

Routing Protocols - How routing works in different topologies
Transport Protocols - TCP vs UDP for star vs mesh

Real-World Applications:

Tools and Frameworks:

Network Planning Tools - Topology simulators
IEEE 802.15.4 - Physical layer for mesh networks

12.17 Try It Yourself: Design Your Own Deployment

Scenario: You’re deploying sensors in a 5-floor office building.

Given:

20 sensors per floor (100 total)
Sensors are battery-powered (target 3 years)
Each floor has concrete walls (RF obstacles)
Budget: $10,000
Uptime requirement: 99.9%

Tasks:

Calculate costs for 3 topologies:
- Pure star (Wi-Fi, 1 AP per floor)
- Pure mesh (Zigbee, self-organizing)
- Hybrid (Ethernet backbone + mesh per floor)
Estimate battery life:
- Star: Sensor wakes, connects to AP (200ms), sends data, sleeps
- Mesh: Sensor may relay neighbors’ packets (always listening)
Analyze failure scenarios:
- Star: What happens if 1 AP fails?
- Mesh: What happens if 10 sensors fail?
Make your choice and justify it.

Solution hints:

Star APs: ~$200 each, but battery drain from connection overhead
Mesh devices: ~$35 each, longer battery life, self-healing
Hybrid: Higher capex, but combines best of both

Check your work by comparing to the warehouse example in this chapter.

Match: Selection Criteria to Topology Recommendations

Order: Applying the Topology Decision Framework

Common Pitfalls

1. Selecting Topology Without Quantifying Requirements

“We need good reliability” is not a requirement. Fix: quantify requirements as “99.9% packet delivery ratio over 30 days” before evaluating topologies against them.

2. Applying Academic Topology Rules to Commercial Products

Academic topology models assume homogeneous nodes. Real Zigbee or Thread products behave as cluster-tree or mesh hybrids depending on firmware configuration. Fix: check the protocol specification for the actual topology it implements, not the textbook model.

3. Making an Irreversible Topology Commitment Without a Pilot

Deploying 500 sensors in a star topology and then discovering that the gateway is a bottleneck is expensive to fix. Fix: pilot with 20–30 nodes in the actual RF environment before mass deployment.

4. Ignoring Operational Team Skill Level in Topology Complexity

A mesh network requires more operational expertise than a star network. If the operations team cannot troubleshoot mesh routing issues, the “resilient” design will fail silently. Fix: match topology complexity to the operational team’s capability.

Label the Diagram

Code Challenge

12.18 Summary

Performance comparison shows tradeoffs between range, latency, bandwidth, and cost
Star topology is best for small deployments, high bandwidth, or simple setup needs
Mesh topology excels for reliability-critical, obstacle-heavy, or large-scale deployments
Tree topology suits enterprise-scale, multi-building deployments with professional IT support
Hybrid approaches combine wired backbone reliability with wireless mesh flexibility
The IoT triangle (range, bandwidth, power) means you can only optimize for two of three

12.19 Knowledge Check

Quiz: Topology Selection

12.20 What’s Next

If you want to…	Read this
Study the basic topology types that feed selection decisions	Basic Types
Learn hybrid design patterns for complex requirements	Hybrid Design
Understand the graph-theoretic basis for selection criteria	Topology Analysis
Run a lab exercise applying selection criteria	Topology Lab
See the module comprehensive review	Comprehensive Review