Bridging a queue to multiple destinations DOUBT

[Francisco Crespo Smith]

Hi Guys,

comming accross my notes, and the new documentation i found this

 

on my mind, i remember that the queue where point to point destinations,as for the image i will say that the message will be delivered from queue.foo to queue.bar, and thats it,

but i read the next sentence: "When a bridge exists between two queues, the message is delivered to both queues. The queues operate independently; if the message is retrieved from one queue, that has no effect on the status of the message in the second queue."

so its not clear for me how this queue.foo its working as a TOPICby delivering the message to any consumer in case is more than one,

can someone xplain it for me. its confusing.

[Girija Waghmare]

With a topic you can send messages to multiple consumers directly (without using bridges). Whichis diiferent from what the above scenarioexplains.

With a bridge ,same message can be delivered to multiple detinations - queus/topics (queue.bar, topic.foo), not directly to multiple end consumers.

These destinations will then send the message totheir own consumers.

The scenario you shared can be used by applications when they need a queue for load balancing (queue.foo) ; but at the same time send the same message to mulitiple downstream applications.

[BWCS Team]

I think you are getting confused between transitive nature of bridges and bridges itself. In the diagram above, the messages are copied to both queue.bar and topic.foo. In fact if you have more bridges, each bridged destination will get a copy of the message. But, if you then connect queue.bar to queue.xyz then the message will only be copied from queue.foo to queue.bar and will not further move to queue.xyz. These are two different things. The messages will always move from source to a destination on the bridge.