ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use NATS JetStream durable consumers with explicit acknowledgments and file storage to survive crashes without losing in-flight messages, and understand the latency and idempotency trade-offs.
Wait for publisher confirms before treating a send as successful, and acknowledge consumers only after processing completes, to make RabbitMQ a durable handoff point.
Fire-and-forget publishing hides broker rejections. Publisher confirms let a producer wait for basic.ack or basic.nack per message, reducing silent loss at the cost of tracking outstanding publishes.
rabbitmq