---
title: "#rabbitmq articles | Hashnode"
description: "Explore 306 articles tagged #rabbitmq on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/rabbitmq"
---

Tag

# #rabbitmq

306 posts · 138 followers

[Somesh Banerjee](https://hashnode.com/@someshbanerjee) · [1d ago](https://hashnode.com/posts/message-broker-using-rabbit-mq/6afc468150bbc072d1ccc531)

### [Message Broker using Rabbit-mq](https://someshbanerjee.hashnode.dev/message-broker-using-rabbit-mq?utm_source=hashnode&utm_medium=feed)

A beginner's guide to creating a message broker using Rabbit-mq. In this project, we will use python and Rabbit-mq for the message broker.

4 min read · [someshbanerjee.hashnode.dev](https://someshbanerjee.hashnode.dev/message-broker-using-rabbit-mq?utm_source=hashnode&utm_medium=feed)

[Waqas Shahid](https://hashnode.com/@practicaldevblog) · [2d ago](https://hashnode.com/posts/rabbitmq-tutorial-an-order-queue-that-never-loses-work/6afaa95de6b1705fee63d091)

### [RabbitMQ Tutorial: An Order Queue That Never Loses Work](https://practicaldevblog.hashnode.dev/rabbitmq-tutorial-an-order-queue-that-never-loses-work?utm_source=hashnode&utm_medium=feed)

Originally published at https://practicaldevblog.blogspot.com/2026/11/rabbitmq-python-order-queue.html Quick answer RabbitMQ is a message broker: one program puts a message into a queue, and another t

9 min read · [practicaldevblog.hashnode.dev](https://practicaldevblog.hashnode.dev/rabbitmq-tutorial-an-order-queue-that-never-loses-work?utm_source=hashnode&utm_medium=feed)

[Stephen Muiruri](https://hashnode.com/@stephen3) · [Oct 26](https://hashnode.com/posts/backend-ecosystem-explained-simply-follow-one-request/6adefe9d18261f3fbe423340)

### [Backend Ecosystem Explained Simply: Follow One Request](https://stephen3.hashnode.dev/backend-ecosystem-explained-simply-follow-one-request?utm_source=hashnode&utm_medium=feed)

Learn how backend technologies like Spring Boot, Docker, Kubernetes, Redis, Kafka, and PostgreSQL work together in a real-world application.

22 min read · [stephen3.hashnode.dev](https://stephen3.hashnode.dev/backend-ecosystem-explained-simply-follow-one-request?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/backend-ecosystem-explained-simply-follow-one-request/6adefe9d18261f3fbe423340)

[Viktor](https://hashnode.com/@viba88) · [Oct 22](https://hashnode.com/posts/did-the-replay-work-finding-the-rabbitmq-dead-letters-that-come-back/6ad9ba789a7428885692e839)

### [Did the replay work? Finding the RabbitMQ dead letters that come back](https://warrenops.hashnode.dev/did-the-replay-work-finding-the-rabbitmq-dead-letters-that-come-back?utm_source=hashnode&utm_medium=feed)

A confirmed replay is not a replay that worked. Tag replayed messages, find the ones that die again, and read the result.

6 min read · [warrenops.hashnode.dev](https://warrenops.hashnode.dev/did-the-replay-work-finding-the-rabbitmq-dead-letters-that-come-back?utm_source=hashnode&utm_medium=feed)

[ZyVOP](https://hashnode.com/@zyvop) · [Oct 21](https://hashnode.com/posts/kafka-vs-rabbitmq-vs-amazon-sqs-which-messaging-system-should-you-use-75rip/6ad86e9ba22aab0d53aef27b)

### [Kafka vs RabbitMQ vs Amazon SQS: Which Messaging System Should You Use?](https://blog.zyvop.com/kafka-vs-rabbitmq-vs-amazon-sqs-which-messaging-system-should-you-use-75rip?utm_source=hashnode&utm_medium=feed)

A practical guide to choosing between three of the most popular ways to move messages between services.

9 min read · [blog.zyvop.com](https://blog.zyvop.com/kafka-vs-rabbitmq-vs-amazon-sqs-which-messaging-system-should-you-use-75rip?utm_source=hashnode&utm_medium=feed)

[Viktor](https://hashnode.com/@viba88) · [Oct 20](https://hashnode.com/posts/replay-only-some-rabbitmq-dead-letters-by-exception-header-or-routing-key/6ad70720ca2952d3c83ec7c9)

### [Replay only some RabbitMQ dead letters: by exception, header or routing key](https://warrenops.hashnode.dev/replay-only-some-rabbitmq-dead-letters-by-exception-header-or-routing-key?utm_source=hashnode&utm_medium=feed)

Put back only the matching dead letters with basic.get, without the nack loop and without losing quorum messages on connection close.

8 min read · [warrenops.hashnode.dev](https://warrenops.hashnode.dev/replay-only-some-rabbitmq-dead-letters-by-exception-header-or-routing-key?utm_source=hashnode&utm_medium=feed)

[Viktor](https://hashnode.com/@viba88) · [Oct 19](https://hashnode.com/posts/your-quorum-dead-letter-queue-can-drop-the-dead-letters-x-delivery-count-travels-along/6ad5b2379f8da2db48e99141)

### [Your quorum dead-letter queue can drop the dead letters: x-delivery-count travels along](https://warrenops.hashnode.dev/your-quorum-dead-letter-queue-can-drop-the-dead-letters-x-delivery-count-travels-along?utm_source=hashnode&utm_medium=feed)

On RabbitMQ 4 a quorum DLQ with a delivery limit can drop messages when they are peeked and put back. Why it happens, and the fix.

7 min read · [warrenops.hashnode.dev](https://warrenops.hashnode.dev/your-quorum-dead-letter-queue-can-drop-the-dead-letters-x-delivery-count-travels-along?utm_source=hashnode&utm_medium=feed)

[Viktor](https://hashnode.com/@viba88) · [Oct 15](https://hashnode.com/posts/masstransit-on-rabbitmq-what-ends-up-in-error-and-skipped-and-how-to-move-it-back/6ad074898cb2984fa69e71da)

### [MassTransit on RabbitMQ: what ends up in \_error and \_skipped, and how to move it back](https://warrenops.hashnode.dev/masstransit-on-rabbitmq-what-ends-up-in-error-and-skipped-and-how-to-move-it-back?utm_source=hashnode&utm_medium=feed)

What MassTransit puts in \_error and \_skipped queues, what the MT-Fault headers say, and how to move messages back without a second delivery.

6 min read · [warrenops.hashnode.dev](https://warrenops.hashnode.dev/masstransit-on-rabbitmq-what-ends-up-in-error-and-skipped-and-how-to-move-it-back?utm_source=hashnode&utm_medium=feed)

[Viktor](https://hashnode.com/@viba88) · [Oct 14](https://hashnode.com/posts/replay-one-message-first-a-canary-for-rabbitmq-dead-letters/6acf20b15277e55e568d3f57)

### [Replay one message first: a canary for RabbitMQ dead letters](https://warrenops.hashnode.dev/replay-one-message-first-a-canary-for-rabbitmq-dead-letters?utm_source=hashnode&utm_medium=feed)

Before replaying a whole dead-letter queue, send one message and watch whether it dies again: how long to wait and what a pass proves.

7 min read · [warrenops.hashnode.dev](https://warrenops.hashnode.dev/replay-one-message-first-a-canary-for-rabbitmq-dead-letters?utm_source=hashnode&utm_medium=feed)

[Viktor](https://hashnode.com/@viba88) · [Oct 12](https://hashnode.com/posts/dead-letters-in-spring-boot-why-rabbitmq-messages-end-up-in-the-dlq-and-how-to-replay-them/6acc9265d3321284aba8b838)

### [Dead letters in Spring Boot: why RabbitMQ messages end up in the DLQ, and how to replay them](https://warrenops.hashnode.dev/dead-letters-in-spring-boot-why-rabbitmq-messages-end-up-in-the-dlq-and-how-to-replay-them?utm_source=hashnode&utm_medium=feed)

Why a failing @RabbitListener ends up in the DLQ, which Spring AMQP settings decide it, and how to put the messages back afterwards.

7 min read · [warrenops.hashnode.dev](https://warrenops.hashnode.dev/dead-letters-in-spring-boot-why-rabbitmq-messages-end-up-in-the-dlq-and-how-to-replay-them?utm_source=hashnode&utm_medium=feed)
