[rabbitmq-discuss] JMS client impl (javax.jms)

Paul Fremantle pzfreo at gmail.com
Wed Nov 17 15:11:09 GMT 2010

> For my own 2 cents: if you want JMS, use a JMS broker like ActiveMQ or
> something. If you're using RabbitMQ, you're doing it because AMQP has things
> that JMS doesn't that make the latter better than the former. If you have to
> stick with JMS because there's a line in the sand somewhere you can't cross,
> I'd almost say just stick with the brokers that more JMS-centric.

I understand your opinion Jon, but my own 2 cents are completely
different. JMS offers a well-understood abstraction to a programming
model. There are some pain points (JNDI), but its very widely used and
adopted. The AMQP working group spent a lot of time ensuring that JMS
can be implemented on top of AMQP. There are a lot of reasons why to

1) Interop with other languages. Because AMQP has clearly defined and
published semantics and a mapping of those to JMS then it makes a good
model where JMS users can use what they know and AMQP users what they
know but everyone can talk.
2) Migration from an existing JMS broker: Users who are using JMS
today may want to position themselves for AMQP in the future.
3) Integration with standard software (e.g. ESBs) that already talk via JMS APIs
4) People who actually like JMS but want the performance, standards
basis, etc of AMQP.
5) People who want to outsource their broker to StormMQ and keep
existing JMS code.


Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

More information about the rabbitmq-discuss mailing list