Skip to content
BENIBIX Learn

Single Point of Failure

Development🏗️ ArchitectureDistributed Systems

Also known as SPOF, Single Point of Failure (SPOF)

One part whose failure stops the whole system.

Think of it like

Think of it like a string of old fairy lights. If one bulb breaks, the whole string goes dark.

Example

Jack's app runs on three web servers but only one database. When the database server's disk fails, all three web servers are useless.

Why it matters

A system is only as strong as its weakest single part. One box you forgot can undo all the other work.

Definition

A single point of failure is one part of a system that stops everything if it breaks. It might be one server, one database, one network cable or one person who knows the password. Finding them is the first step to a reliable system. The usual fix is to add a second copy that can take over. Not every one is worth fixing, so teams start with the ones that would hurt most.

Common mistake

Adding spare servers but leaving one shared thing behind them. It might be one database or one DNS host.

Key takeaways

  1. 1
    One part, all down. That is the risk.
  2. 2
    Find them first. Servers, cables, people.
  3. 3
    Add a second copy. Where it matters most.