liveBook · Manning

Synchronous call

As explained in Clean Applications with Hexagonal Architecture

A synchronous call is an interaction in which the caller waits for the called system to return an answer.

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

How Clean Applications with Hexagonal Architecture covers it

How deep it goes
Explains call flow, waiting costs, and adapter mitigations; defers asynchronous request flows.
Examples
Uses an editor waiting for WriteFlow’s reopen decision before the CMS shows an article as reopened.
What you can do after
Evaluate whether a boundary interaction needs an answer before work can continue, then choose a synchronous call when it does.
How it connects
Contrasts synchronous calls with events and external orchestration, and relates requests to answers and facts to later reactions.

Also explained in

Compare how 12 books explain synchronous call →

Related concepts

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