Coordinating steps.
WHAT IT PROVIDES
A defined sequence of steps, with conditions, retries and error handling, without writing a service.
WHAT IT SUITS
Coordinating calls to several services Processes with defined steps and decisions Work requiring retries and compensation
WHAT IT REPLACES
Chains of functions calling each other, where nobody can see the whole flow.
WHY THAT MATTERS
A defined workflow is visible, and its execution history is inspectable.
WHAT TO DEFINE
Each step, and what it calls Conditions and branches Retry behaviour per step What happens on failure
WHAT COMPENSATION MEANS
Undoing earlier steps when a later one fails.
WHY IT MATTERS
A process failing partway leaves an inconsistent state otherwise.
WHAT TO BE CAREFUL WITH
Workflows containing substantial logic, which belongs in code Long-running steps exceeding limits
WHAT TO KEEP IN THE WORKFLOW
Coordination.
WHAT TO KEEP IN SERVICES
The actual work.
WHAT TO MONITOR
Execution success and duration.
WHAT TO INSPECT AFTER A FAILURE
The execution history, which shows exactly where it stopped.
