Tagged articles
manual ACK
13 articles · Page 1 of 1
RabbitMQ achieves consumer‑side throttling by configuring basic.qos with a prefetchCount, disabling automatic ACK, and using manual ACK so that the broker only pushes a limited number of unacknowledged messages, with detailed guidance on parameter settings, pitfalls, and code examples.
JavaRabbitMQbasic.qos
0 likes · 10 min read

This guide explains the fanout (publish/subscribe) pattern in RabbitMQ, compares it with other exchange types, clarifies common misconceptions, and provides a step‑by‑step Spring Boot implementation—including configuration, producer, multiple consumers, testing, and best‑practice recommendations.
Message BroadcastingPublish‑SubscribeRabbitMQ
0 likes · 10 min read

The article breaks down RabbitMQ's three‑stage message flow—producer to broker, broker persistence, and broker to consumer—detailing how Publisher Confirm, durable exchanges/queues/messages, and manual consumer acknowledgments together guarantee reliability while discussing performance trade‑offs, high‑availability clustering, and common interview follow‑up questions.
Dead Letter QueueMessage ReliabilityPublisher Confirm
0 likes · 14 min read

Learn how to prevent message loss in RabbitMQ by addressing three critical failure points—producer‑to‑broker, broker storage, and broker‑to‑consumer—using publisher confirms, durable queues with persistent messages, cluster mirroring, and manual consumer acknowledgments, complete with Java code examples.
JavaMessage QueuePublisher Confirms
0 likes · 11 min read

This article explains how to achieve near‑zero message loss in RabbitMQ by using producer confirm mode, durable exchanges/queues/messages, database‑backed message compensation, and manual consumer acknowledgments, providing a complete end‑to‑end reliability strategy.
Publisher ConfirmRabbitMQmanual ACK
0 likes · 9 min read

This article demonstrates how to integrate Spring Boot with RabbitMQ using a direct exchange, configuring queues, producers, and two consumers, and explains manual acknowledgment mechanisms (ACK, NACK, Reject) to ensure reliable message processing and handling of consumer failures.
Consumer FailureDirect Exchangemanual ACK
0 likes · 14 min read

This article explains the three stages where RabbitMQ messages can be lost and presents a comprehensive reliability strategy—including producer confirm mode, durable exchanges/queues, message persistence, database‑backed compensation, and manual consumer acknowledgments—to achieve virtually loss‑free message delivery.
Confirm ModeMessage ReliabilityRabbitMQ
0 likes · 9 min read

This article explains how to guarantee almost 100% reliability of messages in distributed systems by examining RocketMQ’s three‑stage reliability model and RabbitMQ’s confirm, persistence, and manual‑ack mechanisms, plus a database‑backed compensation strategy for extreme failure cases.
Message QueueMessage ReliabilityRabbitMQ
0 likes · 11 min read

This article explains how to achieve near‑zero message loss in RabbitMQ by using producer confirm mode, persisting exchanges, queues and messages, storing messages in a database for compensation, and switching consumers to manual acknowledgment, complete with Java code examples.
Confirm ModeJavaMessage Reliability
0 likes · 8 min read

This guide explains how to achieve 99.999999% reliability in RabbitMQ message delivery by using publisher confirms, persisting exchanges/queues/messages, storing outbound messages in a database, and switching consumers to manual acknowledgments to prevent loss in extreme failure scenarios.
BackendMessage ReliabilityPublisher Confirm
0 likes · 9 min read

This article explains the three stages of RabbitMQ message flow, identifies potential loss points, and provides practical solutions—including confirm mode, message persistence, database-backed compensation, and manual acknowledgments—to achieve near‑perfect reliability for both producers and consumers.
Confirm ModeMessage ReliabilityRabbitMQ
0 likes · 10 min read

This article explains how to guarantee message durability, delivery confirmation, manual acknowledgments, TTL, queue length limits, dead‑letter handling, prefetch settings, and routing strategies in RabbitMQ, providing practical code examples and best‑practice recommendations for robust backend systems.
Confirm ListenerRabbitMQdead-letter-exchange
0 likes · 24 min read


JavaEdgeNov 14, 2020 · Backend Development
When a RabbitMQ server accumulates thousands of pending messages, a newly started consumer can be flooded, causing performance degradation or crashes, so this guide explains how to use RabbitMQ's QoS settings and manual acknowledgments to throttle consumers and keep the system stable.
Consumer Flow ControlMessage QueueQoS
0 likes · 5 min read
