Header exchange is not implemented in MB4. We will add it to the roadmap. But IMO we can do what you are suggesting using Topic exchange and message selectors in MB4.
On Sun, Jun 24, 2018 at 1:43 AM Hasitha Hiranya <[email protected]> wrote: > Hi Asitha, > > Did you mean this feature is already implemented in MB4? > If not shall we consider it to the roadmap? > > Thanks > > On Sat, Jun 23, 2018 at 7:00 AM Asitha Nanayakkara <[email protected]> > wrote: > >> Header based routing can be done in AMQP. We can bind multiple queues >> with same routing key (that would be the queue name) with bindings having >> different header attributes. This is done through the header exchange. I'm >> afraid we don't have this in current MB products. Might be a good feature >> to have in upcoming broker product. >> >> In the upcoming broker product we might be able to do something similar >> using the Direct/Topic exchange with message selectors. To configure >> routing (bindings), we need to have an AMQP client or configure using the >> REST API. >> >> Regards, >> Asitha >> >> On Sat, Jun 23, 2018 at 2:42 AM Hasitha Hiranya <[email protected]> >> wrote: >> >>> 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 >>> >> >> >> -- >> *Asitha Nanayakkara* <http://asitha.github.io/> >> Associate Technical Lead >> WSO2, Inc. <http://wso2.com/> >> Mob: +94 77 853 0682 >> [image: https://wso2.com/signature] <https://wso2.com/signature> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > *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 > -- *Asitha Nanayakkara* <http://asitha.github.io/> Associate Technical Lead WSO2, Inc. <http://wso2.com/> Mob: +94 77 853 0682 [image: https://wso2.com/signature] <https://wso2.com/signature>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
