Integrations
How Queuert plugs into your database, broker, schema library and telemetry, and what each adapter kind is for.
Queuert reaches your database, message broker, schema library and telemetry through adapters, which createClient and createWorkerRunner consume. This section has an overview page per adapter kind and a page per backend.
your app
client.createChain(…) attemptHandler complete(…)
queuert
createClient createWorkerRunner
state
stateAdapterrequireddatabase- PostgreSQL
- SQLite
- MySQL / MariaDB
- Redis
- in-process
notify
notifyAdapteroptionalbroker- LISTEN/NOTIFY
- Redis
- NATS
- in-process
observability
logobservabilityAdapteroptionaltelemetry- console
- Pino
- Winston
- OpenTelemetry
validation
jobTypesrequiredschema library, optional- Zod
- Valibot
- TypeBox
- ArkType
Adapter kinds
State adaptersRequired. Where chains, jobs and workers are stored. With a database backend, chains start inside your own transaction: if it rolls back, the chain is never created.Notify adaptersOptional. Wake workers the moment a job is scheduled, and callers awaiting a chain the moment it completes. Without one, the client wakes only its own worker runners; workers in other processes poll.ValidationJob types are required; checking job inputs and outputs at runtime with your schema library (Zod, Valibot, TypeBox, ArkType) is optional.ObservabilityOptional. Structured logs through your logger, metrics and traces through OpenTelemetry, and an embeddable web UI for chains, jobs and workers.