liveBook · Manning

Graceful failure

Also called graceful degradation

Graceful failure is the controlled handling of errors or component failures that preserves essential or acceptable system behavior when possible.

How 3 Manning books explain it

AI Governance

Graceful failure is a system-design approach that limits harm and preserves safe behavior when a process halts or encounters an error.

How it is used
Contains agentic-system risk during suspicious behavior or workflow interruption while preserving safe operation.
How deep it goes
Defines restriction, blocking, and escalation responses but does not detail recovery implementation.
Examples
Uses a half-processed claim, narrowed tool access, added approvals, and policy-enforced escalation.
What you can do after
Operate agent workflows by restricting actions, blocking unsafe runs, and escalating halted work to humans.

Read how AI Governance explains graceful failure →

Clean Applications with Hexagonal Architecture

A pattern in which a system returns reduced functionality or results when a dependency is unavailable while preserving required behavior and invariants.

How it is used
Preserves domain invariants by reducing optional results or skipping optional work when a dependency is unavailable.
How deep it goes
Distinguishes safe degradation from required checks and describes circuit-breaker thresholds, cooldown probes, and fast failure.
Examples
Uses a cached or omitted author display name as fallback, but rejects approval when author validation is unavailable.
What you can do after
Apply the pattern by classifying dependency answers as optional or invariant-gating, then degrading only the former.

Read how Clean Applications with Hexagonal Architecture explains graceful failure →

Grokking Software Architecture

A resilience pattern in which a system continues providing reduced functionality when components or dependencies fail.

How it is used
Keeps applications fast and resilient by providing graceful degradation alongside retries and caching.
How deep it goes
Names graceful degradation as a resilience technique without detailing its behavior or implementation.
What you can do after
Apply graceful degradation alongside retries and caching to help keep an application fast and resilient.

Read how Grokking Software Architecture explains graceful failure →

Also covered in

What to know first

Related concepts

Questions about graceful failure

What is graceful failure?

Graceful failure is the controlled handling of errors or component failures that preserves essential or acceptable system behavior when possible.

Which Manning books explain graceful failure?

AI Governance, Clean Applications with Hexagonal Architecture and Grokking Software Architecture.

What should I know before learning graceful failure?

Manning books that teach graceful failure usually introduce circuit breaker pattern, latency, API gateway and guardrail first.

What is graceful failure also called?

Graceful failure is also called graceful degradation.

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.