Home › Key concepts › Queues and asynchronous work
Key concept · Walk (intermediate) · the same on every platform
Queues and asynchronous work
Hand work to another part of the system to do later, safely.
What it is
A queue holds messages until a worker processes them. The sender does not wait, and if the worker is down, messages wait instead of being lost. A dead-letter queue keeps messages that failed too often, for a person to look at.
Why it matters
It lets parts of a system fail and scale separately.
An example
Checkout puts 'order placed' on a queue; email, stock and invoicing workers each pick it up in their own time.
The common mistake
Processing everything inside the web request, so a slow email service makes checkout time out.
Where you meet it on each platform
The idea stays the same; only the product name changes.
| Job | AWS | Azure | Google Cloud | Databricks | Open source |
|---|---|---|---|---|---|
| Queues and eventshand work to another part safely, even when it is down | SQS / EventBridge | Service Bus / Event Grid | Pub/Sub | Jobs triggers | RabbitMQ or Redis |
Related ideas
Where it shows up
Part of the Walk level on these paths: Software Engineering (building services).