[rabbitmq-discuss] Exactly Once Delivery

Tony Garnock-Jones tonyg at rabbitmq.com
Sat Aug 7 21:13:07 BST 2010

Matthias Radestock wrote:
> So, for example, using publisher-supplied message ids for de-duping
> simply does not scale. Think what a genuine cloud messaging system would
> have to do to handle the case where a producer injects the same message
> first in a node in Australia and then in New York.

What is the problem you're thinking of? Would a setup like the following cope?

 - publishers choose a message ID
 - publishers choose a TTL
 - receivers dedup based on message ID
 - receiver's dedup buffer is expired by (some factor of) TTL
 - each delivery contains an address to which the ACK should be routed


More information about the rabbitmq-discuss mailing list