Here is some details: https://www.rabbitmq.com/confirms.html#publisher-confirms-latency https://www.rabbitmq.com/confirms.html#publisher-confirms-la... To ful

Here is some details: https://www.rabbitmq.com/confirms.html#publisher-confirms-latency https://www.rabbitmq.com/confirms.html#publisher-confirms-la... To fully guarantee that a message won't be lost, it looks like you need to declare the queue as durable + to mark your message as persistent + use publisher confirm. And it looks like this costs you several hundreds milliseconds of latency.