Bulkheading
In order to prevent a situation in which one of the dependencies uses the whole thread pool of an application, Hystrix keeps the thread pool for each dependency. If one of the dependencies becomes latent, it will keep all its threads busy and will reject further invocations, resulting in an increased failure count. Such a strategy is called bulkheading.
This time, the nomenclature is taken from ship engineering: the hull of the ship is divided into isolated bulkheads so that the hull damage in one place results in only one bulkhead being filled with water. Similarly, providing a thread pool for each of the dependencies results in only a dedicated thread pool being used if one of the services is misbehaving.
In complex distributed ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access