Workers and background execution
Dispatch typed background work and observe its lifecycle independently of a request or UI.
Move execution behind an explicit queue
Worker definitions describe input/output contracts; WorkerRuntime binds and executes handlers. WorkerDispatcher starts runs and returns observable handles. Use in-memory execution locally or an explicitly selected queue adapter.
- Define and run a worker for a local typed job.
- Redis queues for an independent transport.
- Persistence, controls and recovery for durable admission and projections.
Do not infer a workflow engine
One WorkerRuntime consumes one command at a time. Scale with independently owned runtimes or processes. Typed handlers are start-only; they do not implement resumable Workflow graphs or cron scheduling.
Redis queue retention is not the durable run ledger, and cancellation does not undo committed effects. Production handlers still need idempotency and explicit recovery ownership.