Mule JMS Queue Configuration Recommendation

Question

I am working on updating the existing Mule configuration, and the task is to improve it to route messages to different endpoints depending on some message properties, so it would be nice to have some pros and cons on two parameters at hand:

• Add message properties using the message-properties-transformer, which is later used by the filter-router, to select the message and place it on the correct endpoint. This option allows me to use one queue for all recipients.

• Create one queue for each destination, and instead add some property for subsequent routing, I just put it in the right queue right away. That is, this parameter will mean one queue for each destination.

Any feedback would be appreciated. Are there any “best practices” regarding this?

Answer 1

I have had great success using your first filter router approach. This reduces cohesion between message producers and consumers. It forms a valuable abstraction, so any service can blindly delete messages inside the general "outgoing".

, . mule, .

, , .

,