A bulkhead pattern isolates resources used by different operations or dependencies so that one failure or overload does not exhaust shared capacity.
A bulkhead limits outstanding calls to a downstream service and fails fast when the limit is reached. This helps synchronous callers contain overload and protect their performance objectives. section 8.2.4
API composition
An API composer calls provider services through proxies. Each proxy can use a bulkhead to limit outstanding calls; circuit breakers and time limiters can provide additional resiliency. section 8.2.4section 12.3.3
How Microservices Patterns, Second Edition covers it
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.
How it connects
Pairs bulkheads with circuit breakers, time limiters, retries, rate limiters, and fallbacks for synchronous communication.
Spring Microservices in ActionA pattern that isolates calls to distributed resources so that a failure or misbehavior in one does not affect the rest of an application.
Grokking Software ArchitectureA resilience pattern that isolates resource capacity into compartments so a failure or slowdown in one area does not exhaust resources elsewhere.
client resiliency patternkind of · A client-side design pattern that helps a service consumer manage failures or performance problems when calling a remote service.
resiliencekind of · Resilience is the ability of a system to continue providing acceptable functionality or recover when failures or other disruptions occur.
thread pooluses · A thread pool is a managed collection of reusable worker threads that execute submitted tasks, typically avoiding the creation of a new thread for each task.
circuit breaker patterncontrasts with · 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.
fault isolationequivalent to · Fault isolation is the containment of a component failure so that it does not propagate to unrelated system components or users.
Hystriximplemented by · Hystrix is a Netflix Java library for fault tolerance in distributed systems, providing circuit breakers and mechanisms for isolating failures and handling fallbacks.
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.