# Message Queues

DevFeed: [Message Queues](<https://devfeed.tech/articles/message-queues-111142.md>)

Original publisher: [Read original article](<https://blog.alexewerlof.com/p/message-queues>)

Author: Alex Ewerlöf

Published: 2026-11-02T05:30:53Z

Content type: article

Language: en

Sources: [Alex Ewerlof Notes](<https://devfeed.tech/sources/alex-ewerlof-notes.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [decoupling](<https://devfeed.tech/topics/decoupling.md>), [backpressure](<https://devfeed.tech/topics/backpressure.md>), [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [admin](<https://devfeed.tech/tags/admin.md>), [ads](<https://devfeed.tech/tags/ads.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [all](<https://devfeed.tech/tags/all.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [message](<https://devfeed.tech/tags/message.md>), [message-queues](<https://devfeed.tech/tags/message-queues.md>), [queues](<https://devfeed.tech/tags/queues.md>), [resilient-architecture](<https://devfeed.tech/tags/resilient-architecture.md>)

## AI overview

Message queues let producers hand work to separate consumers, shortening user-facing waits, isolating worker failures, and buffering traffic spikes. Consumers acknowledge completed messages; if a worker fails before acknowledging, messages can be redelivered, so at-least-once delivery may cause duplicates and works best with idempotent processing. The text recommends queues for asynchronous work, bursty traffic, decoupled scaling, and reliability, while warning they add latency to time-sensitive synchronous workloads. It explains partitioning, ordering versus even workload distribution, back pressure, retry limits and dead letter queues, and durable storage with replay. Kafka retains messages for a configured period and scales through partitions and consumer groups; SQS is managed and offers Standard queues with best-effort ordering or FIFO queues with strict ordering and lower throughput; RabbitMQ uses exchanges and bindings for complex routing.

## Source excerpt

Part of resilient architecture patterns series