Hi. Do we have an opportunity to use x-cache-ttl with queue level deduplication? about rabbitmq-message-deduplication HOT 2 CLOSED

Ok, thank you a lot for your explanation. Will try to use exchange level deduplication in my case.

from rabbitmq-message-deduplication.

Hello,

x-cache-ttl is valid only for exchange level deduplication.

Queue level deduplication is based on the queue content. This means a message is deduplicated until it's in the queue. Hence there is no need to set a TTL as the amount of time a message is deduplicated depends on when it is consumed. A side-effect to be aware of, is that if your queues are empty (because consumers are fast) the queue level deduplication is mostly useless.

The exchange level deduplication is the more generic solution as allows you to control for how long a message should be considered unique.

Queue level deduplication is to be considered in corner cases where, for example, you want to ensure two or more messages of the same type are not consumed at the same time by different consumers but still two messages temporarily close to each other should. You can achieve this by combining deduplication and acknowledgment.

from rabbitmq-message-deduplication.