0 views collected around this technical thread.
Effective software resilience requires strategies such as dead‑letter queues, feature toggles, robust design patterns like bulkhead and circuit breaker, loose coupling, and sidecar containers, enabling developers to isolate failures, reduce impact, and maintain performance in distributed, cloud‑native systems.
This article explains what dead letters are in RabbitMQ, outlines their common causes, and provides a complete Spring Boot configuration and code examples for setting up dead‑letter exchanges, queues, TTL handling, message rejection, and consumer processing to reliably manage undeliverable messages.
This article explains what a Message Queue (MQ) is, why it is used for traffic shaping, system decoupling, and asynchronous processing, reviews popular MQ products such as Kafka, ActiveMQ, RocketMQ and RabbitMQ, and details RabbitMQ's core concepts and advanced features like dead‑letter, delayed, idempotent, priority, and lazy queues.
This article explains the purpose of message queues, outlines RabbitMQ's architecture, describes common MQ patterns such as simple, work, fan‑out, direct, and topic, and discusses reliability features like transactions, confirms, dead‑letter queues, TTL, clustering, and ordering guarantees.
This article explains the concept of RabbitMQ dead letter queues, outlines the conditions that generate dead letters, provides step‑by‑step configuration instructions, and includes Go code examples for publishing messages with TTL and consuming from the dead‑letter queue to implement delayed processing.
This guide explains RabbitMQ dead‑letter queues, covering the conditions that turn messages into dead letters, how to configure exchanges and queues with x‑dead‑letter‑exchange, TTL, and max‑length, and provides step‑by‑step Spring Boot code examples for testing each scenario.
This guide explains RabbitMQ dead-letter queues, detailing the conditions that cause messages to become dead letters, how to configure exchanges and queues with x-dead-letter parameters, and demonstrates three testing methods—reject/nack, TTL expiration, and max-length overflow—using Spring Boot code examples.
This article explains why consumer‑side flow control is needed in RabbitMQ, demonstrates how to use the QoS API and basicQos settings, shows practical Java code for limiting consumption, and covers TTL and dead‑letter queue configurations to improve message reliability and system stability.
This article explains how to implement consumer-side flow control in RabbitMQ using QoS settings, demonstrates configuring prefetch limits, shows how to set message and queue TTLs, and provides step‑by‑step code examples for creating producers, consumers, and dead‑letter queues to manage message overload and expiration.
This article explains how using message queues for asynchronous communication decouples services, improves fault tolerance, and enhances performance, illustrated with a real‑world early‑education app case and a guide to employing dead‑letter queues for handling failed messages.