liveBook · Manning

Coordinator

As explained in Clean Applications with Hexagonal Architecture

A software component that coordinates interactions among other components or processes.

For a process that spans interactions, a coordinator is the external orchestrator that holds the sequence durably so it can recover after failure. section 10.4

Choose coordination by how the work runs:

  • Keep orchestration in the handler when steps run in-process and finish within the request; this is not an integration mode. section 10.4
  • Use events when each system can advance by reacting to received facts. section 10.4
  • Use external orchestration when one place must hold a longer sequence and recover it after failure; do not turn the coordinator into a general message bus. section 10.4

WriteFlow publishing

An inbound request drives the use case, the handler orchestrates local steps, and the use case publishes a fact for other systems. A longer process spanning interactions may need external orchestration. section 10.4

How Clean Applications with Hexagonal Architecture covers it

How deep it goes
Distinguishes handler-local work, event-driven reactions, and external orchestration; defers choosing the coordinator tool.
Examples
Contrasts handler-driven WriteFlow publishing with a longer cross-interaction process that may require external orchestration.
What you can do after
Evaluate whether a process needs durable external orchestration rather than handler-local coordination or event-driven reactions.
How it connects
Connects external orchestration to handlers, events, synchronous calls, and the request-versus-fact distinction.

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.