Sun Devil
Sun Devil

Reputation: 21

Mule ESB act as proxy for AMQP Service (RabbitMQ)?

All,

We are considering Vnext ESB and Messaging solutions in my enterprise. Question on a pattern - Would using Mule ESB to proxy a messaging solution such as RabbitMQ be a viable and supported pattern for Mule?

More specifically, the pattern would include hosting a public JMS Proxy on Mule, Mule receives the message using the JMS protocol and then transforms it to AMQP Protocol before it is sent to RabbitMQ Queue on the outbound. If supported, what is the name of this pattern? Bridge Pattern? Messaging Service Proxy Pattern? Could we employ the JMS, RabbitMQ and/or AnyPoint Connectors to help do this?

The intent for this pattern would be to allow non-AMQP supported (e.g. JMS only) messaging producers in the enterprise to leverage our potential RabbitMQ messaging solution.

The pattern could be further extended to practically any protocol/transport on the inbound - SOAP, REST, Flat file, etc. Yes? No?

Thanks in advance!

Upvotes: 0

Views: 322

Answers (1)

Seba
Seba

Reputation: 2319

You don't need any particular pattern for that. You can simply use any inbound endpoint (JMS, File, JDBC, etc.), then do whatever transformation if required and finally send it to AMQP.

That's one of them main intents of Mule ESB, to abstract you from protocols and transports.

Upvotes: 1

Related Questions