Build your own webhook transport
How to build a webhook registry and delivery system on Postgres using outbox rows, delivery attempts, signatures, retries, and inbound inbox rows.
Domain event, outbox row, or event-store record?
Use ownership, retention, and replay rules to tell domain events, outbox messages, queue jobs, and event-store records apart.
Optional extension: build a small workflow engine in Postgres
When a service-local process outgrows one queue row, add explicit workflow state, step scheduling, timers, signals, and versioning.
Diagnose a slow Postgres work queue
Separate claim-query cost, handler capacity, hot keys, and transport limits before changing queue technology.
Reference: schema, support queries, and guarantee tests
The Postgres schema, operational queries, and tests used to inspect and verify the durable-work implementation.
Cross-service handoffs
Transactional outbox, transport choices, webhooks, contracts, and when brokers fit. Work that leaves your database commit.
Choose the right durable-work shape
How to choose inbox, outbox, projection, CDC, and saga patterns when implementing durable work in Postgres.
Production controls
Lease renewal, fencing, graceful drain, and housekeeping for Postgres-backed durable work after order:9182 ships.
Stable worker affinity with consistent hashing
Use fixed database buckets, a consistent-hash ring, and live membership when work benefits from staying on the same process.
Many workers
Multi-worker contention, delivery guarantees, and per-key ordering before consistent hash.
Crash recovery
Leases, lease cleanup, at-least-once delivery, and handler idempotency for Postgres inbox workers.
The claim loop
Minimal Postgres claim loop: enqueue, SKIP LOCKED claim, complete, and handler retry with an interactive simulation.
A practical guide to durable work in Postgres
Choose and build Postgres-backed work queues with leases, idempotent handlers, competing consumers, outbox delivery, and dead letters.