liveBook · Manning

Bulkhead

As explained in 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.

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.4 section 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.

Also explained in

Compare how 3 books explain bulkhead →

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.