liveBook · Manning

Blocking chain

As explained in Grokking Software Architecture

A blocking chain is a sequence of dependent operations in which delay or failure in one operation prevents subsequent operations from proceeding.

A blocking chain forms when a slow downstream operation makes the caller wait, holding up later work and dragging down the system. The longer the chain, the more one delay can stall. section 6.2.3

Separate the communication handshake from the work it triggers. The caller can receive an acknowledgment while the actual work continues asynchronously, rather than waiting for every operation to finish. section 6.12 section 6.2.3

Release the caller early

Return a receipt such as “202 Accepted” to close the communication loop. Continue the work in the background, then deliver results later through a callback or polling. section 6.2.3 section 6.2.3

How Grokking Software Architecture covers it

How deep it goes
Defines the failure pattern and explains early acknowledgment, background work, callbacks, and polling.
Examples
Uses a 202 Accepted receipt, background work, and callbacks or polling to illustrate early release.
What you can do after
Apply the communication-flow distinction by acknowledging requests early and returning results later through callbacks or polling.
How it connects
Connects synchronous communication with asynchronous flow and relates blocking chains to temporal chains and distributed monoliths.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.