Node/
Modules
The optional subsystems that sit on top of the core queue — workflows, durable steps, the dashboard, injection, mesh, executors, autoscaling.
The optional subsystems that sit on top of the core queue — workflows, durable steps, the dashboard, injection, mesh, executors, autoscaling.
Everything here is optional. The core queue — tasks, jobs, workers, results — is complete without a single one of them, and you can adopt any module on its own without adopting the rest. Each one has its own section; this page is the map, and the last section on it is the bar a new module has to clear.
If you are still working through the basics, none of this is required reading yet. Finish the quickstart first and come back when you hit the problem a module solves.
This list is meant to stay short. A subsystem gets a section of its own — and a card above — only when the first two of these hold. The third holds for every module listed here, so a proposal that fails it owes an argument, not an exemption:
Most of flexiq fails that test, on purpose. Retries are one option on a task, so they sit with the rest of day-to-day queue behaviour in Guides. You always pick a storage backend, so backends sit with the rest of running flexiq in production under Operate. The engine underneath all of it, modules included, is described in Architecture.