Three-tier vs. collapsed core: choosing the right campus design

The three-tier model (access/distribution/core) is the textbook answer, but a lot of real campuses run fine on a collapsed core — distribution and core merged into one layer — and forcing three tiers onto a small site just adds hops and hardware nobody needed.

When collapsed core is the right call

A single building, or a small handful of buildings close together, rarely generates enough inter-block traffic to justify a dedicated core layer. Collapsing distribution and core into one pair of high-capacity switches gives you redundancy and routing without an extra layer of cabling, licensing, and failure domains to manage. Most campuses under a few thousand devices are well served by this.

When you actually need three tiers

The signal isn't device count alone — it's the number of independent distribution blocks. Once you have multiple buildings, each with its own distribution pair, a dedicated core stops being overhead and starts being the thing that keeps adding a building from meaning "redesign the backbone." The core's job — fast, policy-free transit between blocks — only earns its keep once there's more than one block to connect.

The migration path most people miss

You don't have to pick one model forever. A well-designed collapsed core can become the first distribution block of a future three-tier design — as long as the addressing plan and physical cabling left room for a core layer to be inserted later without renumbering. Design collapsed-core deployments as if a core might get added, and the eventual migration is a cutover, not a rebuild.