Hi Team, One of our customer is using WSO2 MB to have one in-queue, and many out-queues. Depending on properties of messages (sometimes looking at payload) they need to route messages conditionally from in-queue to the out queues.
Due to performance reasons, they suggest to have rule based routing / or at least java extension to route to different queues within MB itsself from one queue, without changing the message at all. They also suggest a feature - copy on publish. That means while you are publishing a message to a queue, a copy is stored in another queue for auditing/backup etc. AFAIR, during ESB and MB integration discussions, we decided to have all routings in ESB and have MB as a store only. But when come to performance, this has a impact (as EI have to subscribe and re-publish in JMS way) and having a single hot queue is not also scalable. Is it a enough reason to think on having routing rules within MB itself? Thoughts? Thanks -- *Hasitha Abeykoon* Associate Technical Lead; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
