liveBook · Manning

Fault isolation

Fault isolation is the containment of a component failure so that it does not propagate to unrelated system components or users.

How 3 Manning books explain it

Akka in Action, Second Edition

Fault isolation is the containment of a component failure so that the failed component can be terminated without necessarily stopping unrelated components.

How it is used
Applies supervision to contain actor failures while preserving unrelated message-processing components.
How deep it goes
Contrasts direct object graphs and exception propagation with actor termination, replacement, restart, and mailbox suspension.
Examples
Uses a FileWatcher, LogProcessor, Writer, database connection, corrupted files, and unparseable lines.
What you can do after
Operate/configure actor supervision to terminate, restart, or replace failed actors without disrupting unrelated actors.

Read how Akka in Action, Second Edition explains fault isolation →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

Fault isolation is the containment of a failure within one component so that it has minimal effect on other components or users.

How it is used
Contains microservice failures so users retain unrelated application functions during partial outages.
How deep it goes
Explains containment through timeouts, retries, circuit breakers, and bulkheads, with implementation examples for timeouts and retries.
Examples
Uses a failed video-upload service, Dropbox requests, Axios configuration, and a bounded JavaScript retry function.
What you can do after
Operate/configure microservice requests with bounded timeouts, retries, and user-visible degraded behavior.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains fault isolation →

Microservices Patterns, Second Edition

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

How it is used
Diagnoses a reliability weakness in a monolithic application whose modules share one process.
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.

Read how Microservices Patterns, Second Edition explains fault isolation →

Related concepts

Questions about fault isolation

What is fault isolation?

Fault isolation is the containment of a component failure so that it does not propagate to unrelated system components or users.

Which Manning books explain fault isolation?

Akka in Action, Second Edition, Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform and Microservices Patterns, Second Edition.

What is the difference between fault isolation and monolithic architecture?

Fault isolation is the containment of a component failure so that it does not propagate to unrelated system components or users. Monolithic architecture is a software architectural style in which an application's major functionality is organized and deployed as a single unit.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.