Job Queues Explained: Retries, Idempotency, and Dead-Letter Queues
A technical guide published on DEV Community breaks down the core challenges of designing reliable job queue systems for backend applications. The article explains three message delivery guarantees —…
Read the full articleYou might also wanna read
Implementing PostgreSQL as a Dead Letter Queue for Event-Driven Systems: A Wayfair Case Study
Learn how to use PostgreSQL as a Dead Letter Queue (DLQ) for event-driven systems. Case study from Wayfair showing how to handle failures in
PostgreSQL as a Practical Alternative to Kafka for Small-Scale Message Queuing
Why you should just use Postgres instead of Kafka for small-scale message queuing and pub-sub patterns. Benchmarks and practical tests inclu
topicpartition.io·8mo ago
Evolution of Network Server Programming Patterns: From Fork() to Worker Threads
There's a network-server programming pattern which is so popular that it's the canonical approach towards writing network servers
Designing Idempotent Pipelines in the Agentic Lakehouse: Eliminating Double-Write Anomalies
Agents retry. Networks fail. Jobs time out after doing some work. APIs return ambiguous responses. Schedulers run the same workflow twice. A
The transactional outbox pattern: keeping a database and Kafka consistent
Wrote this up after one too many "the row updated but the event never fired" incidents. It walks through why the dual-write problem is unavo
PgQue: Zero-Bloat Postgres Queue System Using Pure SQL and pg_cron
PgQue – Zero-bloat Postgres queue. One SQL file to install, pg_cron to tick. - NikolayS/pgque
github.com·2mo ago
Comments
Sign in to join the conversation.
No comments yet. Be the first.