Single Point of Failure (SPOF Pattern)

A component whose failure causes the entire system to fail, creating catastrophic vulnerability disguised as efficient design. SPOFs are common because they emerge naturally from optimization: a centralized database is more efficient than distributed ones, a single decision-maker is faster than a committee, one expert is cheaper than training three. The efficiency logic is sound—until the SPOF fails. The pattern: (1) a component is centralized for efficiency, (2) the system works well, creating no pressure to add redundancy, (3) other components develop deep dependencies on the centralized component, (4) the SPOF fails, (5) the entire system cascades because nothing was designed to function without it. SPOFs in organizations are often people rather than technology: the only person who understands the legacy system, the only person with the key client relationship, the CEO who makes all strategic decisions. The CrowdStrike incident of 2024—a single software update crashing 8.5 million Windows computers worldwide—demonstrated a global-scale SPOF in IT infrastructure.

When to use it

During system architecture reviews. When one person holds critical knowledge or relationships. When evaluating infrastructure robustness. When designing disaster recovery plans. When anything 'mission critical' has no backup.

How it can help

Provides a systematic vulnerability assessment methodology. (1) Conduct a 'SPOF audit': for every critical function, ask 'If this component fails, what else fails?' Components whose failure affects many others are SPOFs. (2) Apply the 'bus test' for people: 'If this person were hit by a bus, what would break?' (3) Rank SPOFs by impact and probability, then address them through redundancy, documentation, cross-training, or architecture changes. (4) Accept the efficiency cost of redundancy as insurance: maintaining two of something is expensive, but losing the only one is catastrophic. (5) Periodically test SPOF resilience through controlled failures (Netflix's Chaos Monkey approach).