▲
Use case
Priority-aware job processing
Route urgent work ahead of bulk work with four built-in priority levels and least-loaded dispatch — no custom routing rules.
Best for: Applications where some jobs (user-facing, time-sensitive) must jump ahead of batch work.
The problem
- A single FIFO queue means a burst of low-value batch jobs can starve latency-sensitive work.
- Getting priority right in other queues usually means hand-managing a queue per tier and custom routing.
- Uneven worker load leaves some processes idle while others back up.
How FastWorker handles it
- 1 Submit tasks at critical, high, normal, or low priority — the level is a first-class argument, not a separate queue.
- 2 The control plane dispatches each task to the least-loaded subworker at the highest available priority.
- 3 Scale out by launching more subworkers; they register automatically with zero reconfiguration.