🗓️Workflow Orchestration
Also known as Data Orchestration, Pipeline Orchestration, Data Orchestrator
Pipeline steps run in the right order and on time. Failed steps get retried.
Think of it like
It is like a coach with a whistle. Each player waits for the whistle, then runs their part.
Example
Each night at 2 am, an orchestrator loads sales, then builds the reports, then emails the team. If the load fails, the reports wait.
Why it matters
Real pipelines have dozens of steps that depend on each other. Without a tool to run them, someone runs them by hand and skips one.
Definition
Common mistake
Key takeaways
- 1Order. A task starts when the ones before it finish.
- 2Time. Runs start on a schedule or an event.
- 3Recovery. Failed tasks retry, and people get told.