awa
Postgres-native background job queue. Transactional enqueue, heartbeat crash recovery, priority aging, retries with backoff, cron, callbacks, unique jobs, dead-letter queue, and a vacuum-aware storage engine designed to keep dead-tuple pressure bounded under sustained load.
This crate is the user-facing facade. It re-exports the worker
(awa-worker) and model (awa-model) crates and is what most Rust
applications depend on directly.
[]
= "0.6"
Quick start
use ;
use ;
async
async
What you get
- Transactional enqueue — enqueueing a job is a normal
INSERTyou can commit alongside your application's writes. - Vacuum-aware storage — append-only ready entries plus a partitioned receipt ring keep the queue tables' dead-tuple footprint bounded under sustained load. See ADR-019 and ADR-023.
- Crash-safe execution — heartbeat-based lease tracking; jobs whose workers vanish are rescued automatically.
- Per-queue policy — priorities, priority aging, weighted concurrency, rate limits, deadlines, retry/backoff, cron, dead-letter queue.
- Unique jobs — content-keyed deduplication windowed across pending / running / completed.
- Callbacks and external waits — wait for an external event without burning a worker slot.
- First-class Python bindings — same engine, same SQL, same defaults; see awa-pg on PyPI.
Documentation
- Getting started (Rust)
- Configuration
- Architecture
- Migrations
- Upgrading 0.5.x → 0.6
- Dead Letter Queue
- Deployment
- Cross-system benchmark comparison
License
Dual-licensed under MIT or Apache-2.0, at your option.