Ensuring Message Survival: Using NATS JetStream for Durable Event Logs
Standard NATS drops messages during restarts. Learn how to use JetStream to create durable logs and consumers that guarantee at-least-once delivery for critical events.
Loading…
ReadMeFeed / Community knowledge
#message-durability
Real questions. Useful conversations. Find the people who know your stack.
natsRabbitMQ Publisher Confirms: Enabling, Using, and Avoiding Pitfalls
Learn how to enable RabbitMQ Publisher Confirms for reliable message publishing, track unconfirmed messages, avoid common pitfalls, and verify durability in a production‑ready setup.
rabbitmqQuorum Queues Replace Mirrored Queues in RabbitMQ: What Changes for Durability
Quorum queues replace mirrored queues in RabbitMQ with Raft-based replication. A write is acknowledged only after a majority of replicas persist it, changing durability, latency, and operations.
Choosing RabbitMQ Queue Types: Quorum vs Classic Queues
A decision guide for RabbitMQ quorum queues vs classic queues: constraints, trade-offs, and a concrete declaration and validation example.
RabbitMQ Quorum Queues: When Replication Is Worth the Consensus Tax
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.
RabbitMQ Publisher Confirms: Knowing When the Broker Actually Has Your Message
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.