2 posts tagged with "design"

Adding a queue shouldn't mean adding a broker. If you already run PostgreSQL (or SQLite, or Oracle), you already have durable storage, transactions, and — with SKIP LOCKED and LISTEN/NOTIFY — everything a robust queue needs.

You write an order row, then enqueue its fulfillment job. What happens if the process dies between the two? Or the transaction rolls back after the job was queued? You get a job referencing data that doesn't exist — the dual-write bug.