AntifragilityPrinciple

Small local failures (design for them)

Малые локальные провалы · Chaos engineering · Small failures

Build systems where small components fail often, cheaply, and visibly - so the whole system gets information without ever risking ruin.

Plain explanation

Forest fires that are suppressed too well accumulate fuel until a catastrophic fire. Companies that prevent every micro-failure accumulate fragility until a big one. Antifragile design accepts - even invites - small failures as information, then learns from them.

Why it matters

If your system never fails small, it's accumulating the conditions to fail big.

Practical example

Netflix's Chaos Monkey: deliberately kills production services in random patterns. The system has to handle this. Big outages become almost impossible.

How to use

1Where can you afford a small failure today that will teach you something?

Related concepts

Antifragility

AntifragilityNot the opposite of fragile. Beyond robust. Antifragile systems benefit from stress, variation, error, and time.

Antifragility

Via negativaImprove by subtracting harm - not by adding clever fixes. Removing bad inputs is more reliable than adding good ones.

Antifragility

Single point of failureA component whose failure brings down the whole system. The classic structural fragility. Almost always cheaper to remove than to defend.

Read the original book

This part of the knowledge base is inspired by the book. Go to the Ukrainian edition to explore the concept in depth.

Buy «Антикрихкість»

Source notes

· Антихрупкость - local failures