A synchronous call is a direct request in which the caller waits for an answer before continuing. It fits a boundary interaction when the next step depends on that result. section 10.3.1
Inbound, a driving actor calls an endpoint and the use case answers within the same call. Outbound, a handler calls an output port and waits for the output adapter’s result. The adapter can apply timeouts, retries, and failure mapping, but the wait remains. section 10.3.1
CMS reopen decision
An editor waiting in the CMS needs WriteFlow’s decision before an article can be shown as reopened, so the CMS waits for the response in the same call. section 10.3.1
Choose the interaction mode according to what the caller needs:
- Use a synchronous call when the use case cannot continue without the answer. section 10.4
- Use an event when the interaction reports a fact and others can react later; use external orchestration when a coordinator must track a longer sequence. section 10.4











