liveBook · Manning

Bulkhead

The bulkhead pattern isolates resource capacity among workloads or components so that failure or overload in one does not exhaust resources or disrupt others.

How 3 Manning books explain it

Spring Microservices in Action

A pattern that isolates calls to distributed resources so that a failure or misbehavior in one does not affect the rest of an application.

How it is used
Protects a distributed-resource client from one slow or failing call consuming resources needed by others.
How deep it goes
Explains thread-pool isolation and demonstrates command-level pool and queue configuration, including isolation-model and context tradeoffs.
Examples
Uses watertight ship compartments and a license lookup with a dedicated Hystrix thread pool.
What you can do after
Apply it via Spring Cloud and Netflix Hystrix by assigning remote calls to configured thread pools.

Read how Spring Microservices in Action explains bulkhead →

Grokking Software Architecture

A resilience pattern that isolates resource capacity into compartments so a failure or slowdown in one area does not exhaust resources elsewhere.

How it is used
Contains a service failure by preventing it from exhausting resources needed elsewhere in the application.
How deep it goes
Defines hard resource limits and illustrates thread-pool isolation, without detailing implementation tooling.
Examples
Uses watertight ship compartments and a 100-thread application split between web traffic and a Payment API.
What you can do after
Understand how isolating resource capacity can keep unaffected application functions available during a service failure.

Read how Grokking Software Architecture explains bulkhead →

Microservices Patterns, Second Edition

A bulkhead pattern isolates resources used by different operations or dependencies so that one failure or overload does not exhaust shared capacity.

How it is used
Protects synchronous service calls and API-composition provider proxies from downstream overload by limiting outstanding requests.
How deep it goes
Defines a limit on outstanding calls and fail-fast behavior, but does not develop implementation details.
Examples
Uses API Gateway-to-Order Service calls and API-composition provider proxies as synchronous-call settings.
What you can do after
Apply it by capping outstanding synchronous calls and failing fast when the limit is reached.

Read how Microservices Patterns, Second Edition explains bulkhead →

Also covered in

What to know first

Related concepts

Questions about bulkhead

What is bulkhead?

The bulkhead pattern isolates resource capacity among workloads or components so that failure or overload in one does not exhaust resources or disrupt others.

Which Manning books explain bulkhead?

Spring Microservices in Action, Grokking Software Architecture and Microservices Patterns, Second Edition.

What should I know before learning bulkhead?

Manning books that teach bulkhead usually introduce thread pool and circuit breaker pattern first.

What is the difference between bulkhead and circuit breaker pattern?

The bulkhead pattern isolates resource capacity among workloads or components so that failure or overload in one does not exhaust resources or disrupt others. A fault-isolation pattern that temporarily interrupts operations when monitored failures or unsafe conditions meet a defined criterion, limiting cascading effects and allowing recovery checks.

What is bulkhead a kind of?

Bulkhead is a kind of client resiliency pattern. A client-side design pattern that helps a service consumer manage failures or performance problems when calling a remote service.

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.