A service chain is the ordered sequence of services participating in one request or user action. Trace it from the initial gesture through every service, in exact execution order, rather than cataloging related endpoints in isolation. section 8.4
Map representative actions with this workflow:
- Choose six to eight actions that differ in kind: include read-only, write-heavy, scheduled, and admin-only flows. section 8.4
- Render each action as a swimlane diagram, using backend services as lanes and service calls as left-to-right events. section 8.4
- Record lane count, event count, and the lane containing the step that keeps the user waiting. section 8.4
Representative actions
Trace browsing a catalog, placing an order, a nightly abandoned-cart reminder, and an administrator issuing a refund. Each action activates a different service chain. section 8.4
Figure 8.6 A typical API request has three phases: synchronous pre-flight checks the user waits for, a core database transaction, and asynchronous follow-up work that runs after the 201 response is sent.

Use the three-phase request view to distinguish synchronous pre-flight checks, the core transaction, and asynchronous follow-up work within a chain. section 8.4
