Queues
- Parts
- 02
- Minutes to read
- 20
Asynchronous work needs an explicit delivery contract. First, examine the guarantees a task requires and their operational cost. Then explore an experiment with four approaches to task ingestion.
The articles themselves are published in Russian.
What you will explore
- Distinguish business consistency, data durability, and delivery guarantees.
- Check whether a transactional outbox and an idempotent worker are sufficient.
- Compare latency, task accumulation, and recovery after a failure.
Reading order
The first part frames the architectural questions. The second tests alternatives on a specific testbed. Read every measurement together with its experimental conditions.
- 01Why Do You Put Queues Everywhere?Why a broker does not solve business consistency and when a transactional outbox with a worker is simpler than a queue.4 min
- 02Queues Still Are Not Needed: Testing the ClaimA comparison of WAL, an ingest database, Valkey Streams, and RabbitMQ across latency, durability, backlog, and operations.16 min