Execution Backends
Sprocket evaluates a workflow locally and decomposes it into tasks. Sprocket dispatches these tasks to a configured execution backend responsible for starting, monitoring, and responding to task lifecycle events.
Sprocket currently supports two execution backends:
- A local Docker execution backend.
- A remote Task Execution Service backend.
There are two additional execution backends currently under development:
Backend configuration
A sprocket.toml configuration file may contain settings for zero or more execution backends, but currently Sprocket uses only one specified backend during a workflow evaluation.
The execution backend is specified in the run section:
[run]
backend = "<name>"The name corresponds to an entry in the run.backends table. A backend setting is required if there is more than one backend or if the backends table does not contain a default entry.
An example of configuring more than one backend:
[run]
backend = "server1"
[run.backends.server1]
type = "tes"
# ...
[run.backends.server2]
type = "tes"
# ...If no execution backend is configured in sprocket.toml, the Docker backend is used.