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
