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

Tag

# #messaging

244 posts · 17 followers

[Wabbiyo](https://hashnode.com/@wabbiyo) · [Oct 24](https://hashnode.com/posts/creating-whatsapp-message-templates-via-the-cloud-api-payloads-review-and-status-webhooks/6adc6c15d46358abb5a23c05)

### [Creating WhatsApp Message Templates via the Cloud API: Payloads, Review and Status Webhooks](https://wabbiyo.hashnode.dev/creating-whatsapp-message-templates-via-the-cloud-api-payloads-review-and-status-webhooks?utm_source=hashnode&utm_medium=feed)

If you’re building WhatsApp messaging into an app, you’ll want to create and track templates programmatically instead of through WhatsApp Manager. Here’s the flow. Create the template Templates are

3 min read · [wabbiyo.hashnode.dev](https://wabbiyo.hashnode.dev/creating-whatsapp-message-templates-via-the-cloud-api-payloads-review-and-status-webhooks?utm_source=hashnode&utm_medium=feed)

[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 7](https://hashnode.com/posts/reading-the-x-death-header/6ac5dfc9e2a13b6aaef16100)

### [Reading the x-death header: which queue rejected the message, and why](https://warrenops.hashnode.dev/reading-the-x-death-header?utm_source=hashnode&utm_medium=feed)

What every field in RabbitMQ's x-death header means, how it grows across retry queues, and how to read it from the UI, the CLI or code.

8 min read · [warrenops.hashnode.dev](https://warrenops.hashnode.dev/reading-the-x-death-header?utm_source=hashnode&utm_medium=feed)

[Ciphemic academia](https://hashnode.com/@ciphemicacademia) · [Oct 7](https://hashnode.com/posts/kafka-vs-rabbitmq-vs-sqs-the-message-queue-that-started-at-400-000-messages-a-second/6ac5a49b8b4906bc608993f0)

### [Kafka vs. RabbitMQ vs. SQS: The Message Queue That Started at 400,000 Messages a Second](https://ciphemicacademia.hashnode.dev/kafka-vs-rabbitmq-vs-sqs-the-message-queue-that-started-at-400-000-messages-a-second?utm_source=hashnode&utm_medium=feed)

LinkedIn built Kafka because RabbitMQ was two orders of magnitude too slow for their needs.

13 min read · [ciphemicacademia.hashnode.dev](https://ciphemicacademia.hashnode.dev/kafka-vs-rabbitmq-vs-sqs-the-message-queue-that-started-at-400-000-messages-a-second?utm_source=hashnode&utm_medium=feed)

[Sanskriti Harmukh](https://hashnode.com/@sharmukh) · [Sep 30](https://hashnode.com/posts/deploying-fluxer-an-open-source-instant-messaging-and-voip-platform/6abd60586f2a34a6710d8b61)

### [Deploying Fluxer - An Open Source Instant Messaging and VoIP Platform](https://vultr.hashnode.dev/deploying-fluxer-an-open-source-instant-messaging-and-voip-platform?utm_source=hashnode&utm_medium=feed)

Deploy Fluxer with its official Docker Compose stack and Caddy for HTTPS, then create the owner account for a self-hosted chat and VoIP platform.

7 min read · [vultr.hashnode.dev](https://vultr.hashnode.dev/deploying-fluxer-an-open-source-instant-messaging-and-voip-platform?utm_source=hashnode&utm_medium=feed)
