3 ms·
I've never seen that option before - I stand corrected. I'd be interested to see how having it switched on affects performance. Also I expect there are still fe
by mafro 9y ago
I've never seen that option before - I stand corrected. I'd be interested to see how having it switched on affects performance. Also I expect there are still few guarantees about data loss in the event of failure.
- ngrilly 9y agoHere 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.