Understanding workers <> workflows
Hi I am new to workflows and I am wrapping my head around the relationship between workers and worflows. Following is my understanding:
- We need a worker binded to a workflow so that we can trigger the workflow
- There's no other way to create a workflow other than to declare it via a worker
- The workflow step instances are probably individual workers which are
abstracted away from the end user - One worker can be binded to multiple workflows.
- When defining the workflow in the binded worker we do define parameters
(in Params) but these are not specific to any workflow. These are in-code
worker specific construct/convention. Which is why, currently in workflows
web UI, you'd not see any "typed" way to provide parameters. It would
accept just about any JSON you provide. - You'd usually trigger the workflow via the REST API or via the binded
Worker. Trigger via the binded Worker is more preferable to me as it
allows for better error handling and any other processing. Also the
Workflows REST API endpoint is not very well documented.
