Tagged articles
message persistence
15 articles · Page 1 of 1
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

To prevent message loss in RabbitMQ systems, this guide explains the three-step message flow, introduces producer confirm mechanisms, demonstrates how to enable persistence for exchanges, queues and messages, outlines a database fallback strategy, and shows how to implement manual consumer acknowledgments for end‑to‑end reliability.
Consumer AcknowledgmentMessage ReliabilityProducer Confirmation
0 likes · 12 min read

This article explains how to guarantee RabbitMQ message reliability—preventing loss and duplicate consumption—by covering producer‑consumer models, persistence, transaction and confirm mechanisms, consumer acknowledgments, troubleshooting steps, and compensation strategies such as retry queues and idempotent design.
Consumer AcknowledgmentMessage ReliabilityRabbitMQ
0 likes · 14 min read

This guide explains how to implement server‑side WebSocket message persistence using MySQL, covering requirement analysis, database schema design, Think‑ORM integration, event handling code, testing scripts, and performance considerations for high‑concurrency scenarios.
MySQLPHPWebSocket
0 likes · 10 min read

This article explains how to achieve near‑zero message loss in RabbitMQ by using producer confirm mechanisms, durable exchanges/queues, persistent messages, database‑backed message storage, and manual consumer acknowledgments, providing a complete end‑to‑end reliability solution.
Confirm MechanismConsumer AcknowledgmentJava
0 likes · 9 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

The article explains how to achieve near‑zero message loss in RabbitMQ by using producer confirm mode, persisting exchanges, queues and messages, storing outbound messages in a database, and switching consumers to manual acknowledgment with proper retry and idempotency handling.
Consumer AckJavaMessage Reliability
0 likes · 8 min read

This article explains how to achieve high‑reliability message delivery in RabbitMQ by using the confirm publish mechanism, persisting exchanges, queues and messages, storing outbound messages in a database for compensation, and switching consumers to manual acknowledgment to prevent loss in various failure scenarios.
Confirm MechanismConsumer AcknowledgmentJava
0 likes · 9 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

The article explains how to achieve high‑reliability message delivery in RabbitMQ by using producer confirm mode, persisting exchanges, queues and messages, storing outbound messages in a database, and switching consumers to manual acknowledgments to prevent loss in network or broker failures.
Consumer AcknowledgmentJavaMessage Queue
0 likes · 9 min read


21CTOAug 8, 2021 · Backend Development
This article examines how to ensure reliable message delivery in RabbitMQ by using durable queues, the confirm mechanism, and supplemental strategies such as persisting messages to Redis, implementing idempotent processing with optimistic locking or unique‑ID fingerprints, and employing compensation tasks to achieve near‑zero message loss in high‑concurrency systems.
Confirm MechanismIdempotencyOptimistic Lock
0 likes · 9 min read


ITPUBAug 6, 2021 · Backend Development
This article examines common pitfalls in RabbitMQ message delivery, explains persistence and confirm mechanisms, and proposes a robust solution combining pre‑storage in Redis, confirm callbacks, scheduled retries, and idempotent processing to ensure virtually zero message loss in high‑concurrency systems.
Confirm MechanismIdempotencyOptimistic Lock
0 likes · 11 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

This article provides a comprehensive overview of RabbitMQ, covering its origins, core components, message routing patterns, persistence mechanisms, delivery modes, RPC support, clustering design, mirrored‑queue architecture, and flow‑control strategies for building reliable backend systems.
ClusterMessage QueuingRabbitMQ
0 likes · 14 min read

This article explains how to guarantee that order service messages are reliably delivered to RabbitMQ by using durable queues, the confirm mechanism, early persistence with Redis and scheduled retries, and idempotent processing techniques to achieve near‑100% message safety in high‑concurrency environments.
Confirm MechanismIdempotencyRabbitMQ
0 likes · 10 min read
