Implement a durable work queue in Postgres
How to implement common queue and messaging patterns in Postgres: competing consumers, transactional outbox, idempotent handlers, leases, and dead letters.
The claim loop
Minimal Postgres claim loop: enqueue, SKIP LOCKED claim, complete, and handler retry with an interactive simulation.
Crash recovery
Leases, lease cleanup, at-least-once delivery, and handler idempotency for Postgres inbox workers.
Many workers
Multi-worker contention, delivery guarantees, and per-key ordering before consistent hash.
Partitioning at scale
Consistent hash, heartbeats, rebalance windows, and multi-worker simulation with ring ownership.
Production controls
Lease renewal, fencing, graceful drain, and housekeeping for Postgres-backed durable work after order:9182 ships.
Schema and operations
Full Postgres schema, inbox SQL, observability, testing, and schema evolution for order:9182.
Performance and scaling
Claim-path tuning, indexes, and an interactive performance tuner for Postgres claim loops.