technologybriefs
8:47in productionCh. 1 · Why loops kill networks/ 8:47 · ceiling 15 min
Systems

Radia Perlman

STP made Ethernet scale—but at the cost of minutes-long outages every time the network blinked.

Spanning Tree Protocol (STP), invented by Radia Perlman in 1984 at Digital Equipment Corporation, solved catastrophic broadcast storms in bridged LANs by algorithmically disabling redundant links while preserving failover capability. It standardised loop prevention as IEEE 802.1d. Its constant-memory design enabled deployment on resource-constrained hardware. But its ~60-second convergence window created operational fragility during topology changes—a gap later addressed by RSTP and MSTP. STP is foundational infrastructure, not obsolete, but no longer fit for dynamic or high-availability environments.

SystemsAlgorithmsComputingEngineeringAlgorithms across the network →
Chapters & takeaways5
  1. 0:56
    Why loops kill networks

    Loops didn’t just slow traffic—they collapsed bridged networks by flooding frames endlessly.

  2. 2:02
    How STP builds a tree

    It elected a root bridge using MAC addresses, then disabled all but the shortest path to it.

  3. 3:20
    What made it deployable

    Constant memory use let it run on low-end bridges; redundant links gave automatic failover.

  4. 4:38
    Who built it

    Radia Perlman invented both the algorithm and the protocol—not just the idea, but the spec.

  5. 6:03
    The single-path guarantee

    It left exactly one active path between any two nodes—no more, no less.

Worth your time?

Yes. Study the whole thing.

4/ 5
What works
  • Prevents network collapse from loops.
  • Enables automatic failover via redundant links.
  • Runs with constant memory regardless of network size.
  • Standardised interoperability across vendor bridges.
What does not
  • It does not prevent loops in real time.
  • It does not support load balancing across redundant links.
  • It does not scale to mesh or multi-root topologies without extensions.
Study it if
  • Network engineers maintaining legacy enterprise LANs.
  • Students learning how layer-2 redundancy control evolved.
  • Historians of internet infrastructure.
Skip it if
  • Cloud architects designing modern data centres.
  • Developers building distributed systems.
  • Security teams assessing attack surface—STP itself has no security model.
The written brief1 min read

What it is and the problem it solves

Spanning Tree Protocol (STP) is a network control algorithm that prevents broadcast storms caused by loops in bridged local area networks. Loops cause Ethernet frames to flood the network and fail to reach their destination, collapsing connectivity.

How it works

It uses bridges’ unique 48-bit MAC addresses to elect a root bridge. Each bridge maps the network and computes the shortest path to that root. Redundant links are disabled, leaving exactly one active path between any two nodes.

What works

It delivers reliable data over redundant links using automatic failover. It operates with constant memory usage regardless of network size. It standardised loop prevention across vendor bridges as IEEE 802.1d.

What does not

It does not converge quickly: topology changes take up to one minute to stabilise, risking temporary loops and frame flooding during reconfiguration.

What it changes

It changed LAN design from fragile, loop-avoidant topologies to resilient, redundant ones—enabling scalable bridged Ethernet without manual link management.

Is it worth your time

Yes—if you maintain or design bridged Ethernet networks built before 2003, or need to understand why modern alternatives exist. Otherwise, it is legacy infrastructure with known failure modes.

Same field · Systems4 of 25
9:54
5G5G is a defined cellular standard—not a monolithic upgrade. Its real-world impact depends entirely on deployment mode, spectrum choice, and backhaul investment. It enables new use cases only where standalone architecture and mid-band spectrum converge. Elsewhere, it functions as a marketing label atop LTE infrastructure.
8:50
Amazon Web Services2006AWS launched S3 in March 2006 as its first generally available Infrastructure-as-a-Service offering. It evolved from internal Amazon platform standardisation efforts beginning in the early 2000s. Its first developer-facing web services shipped in July 2002. Simple Queue Service (SQS) launched in beta in November 2004 and became generally available in July 2006. EC2 followed in August 2006. AWS was the first cloud provider to build infrastructure specifically for U.S. government security and compliance requirements, launching GovCloud in 2011.
8:32
Bitcoin2009Bitcoin is the first decentralized cryptocurrency. It solves double-spending without a trusted intermediary. Its mechanism relies on proof-of-work mining, public blockchain replication, and cryptographic key control. It delivers decentralisation, Sybil resistance, and Byzantine fault tolerance—but only if users protect private keys. It does not solve scalability, energy use, or usability. It changes what digital money can be—but not what it must be.
11:02
Bjarne StroustrupC++ is a language defined by trade-offs: abstraction without runtime cost, flexibility without enforced safety, evolution without breaking change. Its endurance reflects engineering necessity—not consensus.
Up next in Technology

Raspberry Pi

2012 · 11:02

A $35 board built to fix Cambridge’s admissions crisis became the world’s most widely deployed open-hardware computer—not because it was perfect, but because it was just enough.

Play nextBack to Systems
11:02