Skip to main content

About workers and commands

A worker is a microservice that can contain one or more commands. Commands are triggered by tasks.

Workers are automatically scaled in or out depending on the amount of work available and the worker configuration.

Workers can contain a catalogue of commands:

  • Simple commands without any steps or durable state;
  • Commands with manual state management;
  • Commands without sub tasks, but with durable milestones using steps;
  • Complete orchestrations or workflows, with sub tasks, can act als child workflows.
  • etc.

Durable and stateful commands​

Workers can be scaled in/out, replaced by updated versions or have temporary failures.

To make workers more robust, Taskurai offers some built-in features:

Keeping SDK up to date​

Since Taskurai instances are automatically updated, it is imported to keep the Taskurai SDKs up-to-date. While Taskurai SDKs are designed to be backward compatible, the most recent versions contain improvements and bug-fixes. Updated worker images should be rebuild and redeployed.

Limitations​

Taskurai Worker Containers have the following limitations:

  • Privileged containers: Taskurai can't run privileged containers. If your program attempts to run a process that requires root access, the application inside the container experiences a runtime error.
  • Operating system: Linux-based (linux/amd64) container images are required.
  • Ingress: Ingress is disabled and not possible with Taskurai workers.