ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #rabbitmq
Quorum queues use Raft consensus to keep RabbitMQ messages safe through node failures — but only if publishers, consumers, and queue settings all line up. Here's when the consensus tax is worth paying.
Learn how RabbitMQ dead-letter exchanges capture failed messages for debugging and retry workflows. A practical guide to configuring DLX with TTL and routing keys.
RabbitMQ 4.0 removed classic mirrored queues. Quorum queues use Raft consensus for stronger durability, but require 3+ nodes, more disk I/O, and a migration strategy since in-place conversion isn't supported.
basicPublish returning doesn't mean RabbitMQ stored your message. Publisher confirms give you a per-message ACK after disk write — here's how to enable, track, and verify them without killing throughput.
Learn how to use RabbitMQ’s Dead Letter Exchange to capture expired or rejected messages, with a step‑by‑step example, trade‑offs, and best‑practice checks.
Publisher confirms tell you the broker accepted a message — not that it reached a queue or a consumer. Here's the design that closes the gap.
Guide to decide which Symfony Messenger transport fits your throughput, reliability, and ops constraints, with a ready‑to‑run config example.
Identify why RabbitMQ publisher confirms stall, diagnose queue, memory, network, or client issues, and apply targeted fixes with verification steps.
Dead Letter Exchanges let you isolate failing messages, prevent poison pills, and implement delayed retries. Learn how to configure DLX, TTL-based retry queues, and guard against infinite loops.
symfony