Message Queues
A message queue buffers work between producers and consumers. It lets producers submit tasks without waiting for processing, and lets consumers work at a controlled rate. Correct queue use depends on delivery, acknowledgement, duplicate handling, ordering, expiry, and dead-letter policies.
itDistributed systems, messaging, and integration | OpenSkills.info
Intro
Message Queues
A message queue is a one-way channel for work. A producer submits a message. The queue retains it until a consumer receives and processes it. Acknowledgement tells the queue whether the consumer accepted the work.
A queue separates arrival rate from processing rate. This is useful when incoming demand is bursty or a downstream dependency must be protected. The queue creates time and capacity for recovery. It does not make a permanently insufficient consumer fleet catch up.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://learn.microsoft.com/en-us/azure/architecture/patterns/queue-based-load-leveling
Supports
- Queue buffering
- load leveling
- backlog
- idempotency
- ordering
- dead-letter handling
- and capacity considerations
- https://www.enterpriseintegrationpatterns.com/patterns/messaging/
Supports
- Queue
- competing consumers
- idempotent receiver
- and dead-letter vocabulary
- https://github.com/stn1slv/awesome-integration
Supports
- Message queue ecosystem discovery
- https://www.rabbitmq.com/tutorials
Supports
- Queue tutorial progression
- https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html
Supports
- Managed queue service documentation
- https://nats.io/
Supports
- Persistent work-queue messaging
- https://activemq.apache.org/
Supports
- Open-source messaging