liveBook · Manning

Asynchronous flow

As explained in Grokking Software Architecture

Asynchronous flow is a processing model in which work continues independently after the initiating interaction has completed.

Asynchronous flow lets work continue in the background after the initiating interaction ends. A synchronous API call can start that work without making the caller wait for it to finish. section 6.12 section 6.2.3

A common pattern separates the request from the work:

  • A caller makes a synchronous request to start a slow task. section 6.2.3
  • The service closes the communication loop early, for example with a 202 Accepted response, freeing the caller to move on. section 6.2.3
  • The task continues in the background; results can arrive later through a callback or polling. section 6.2.3

The distinction matters: synchronous communication is the handshake, while asynchronous flow is how the work proceeds. Returning a response early helps prevent one slow task from creating a blocking chain that stalls other services. section 6.12 section 6.2.3

How Grokking Software Architecture covers it

How deep it goes
Distinguishes communication from work and describes early responses, background processing, callbacks, and polling.
Examples
Uses a 202 Accepted response to release the caller, with callbacks or polling to return results later.
What it assumes
Assumes familiarity with the synchronous request-response handshake and distinguishes it from the flow of work.
What you can do after
Apply asynchronous flow by returning early while slow work continues in the background.
How it connects
Connects asynchronous flow to synchronous communication, APIs, and blocking chains.

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.