liveBook · Manning

Fault isolation

As explained in Microservices Patterns, Second Edition

Fault isolation is the ability to contain a component failure so that it does not bring down unrelated components.

Fault isolation contains a component failure so it does not bring down unrelated components. When application modules share one process, a defect in one module can crash the whole application. section 2.1.3

A module failure in FTGO

In FTGO, a memory leak in one module could crash all application instances one by one, causing production outages. section 2.1.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines failure containment and illustrates its absence, but gives no implementation mechanism.
Examples
Uses an FTGO module's memory leak crashing application instances as the failure scenario.
What you can do after
Understand how a shared process lets one module's defect cause application-wide outages.
How it connects
Connects fault isolation to monolithic architecture, application modules, production reliability, and failure diagnosis.

Also explained in

Compare how 3 books explain fault isolation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.