Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.
Hannah Smalltree, Editorial Director
Internally, IBM MQ and MSMQ only implement the message queueing model,
but not the publish/subscribe model. Hence, in IBM MQ, the JMS pub/sub model is
realized atop of message queues, by creating one queue per subscriber,
for example. This works but will not necessarily lead to good
performance or scalability, as the middleware is not aware of pub/sub
communication and thus does not provide any optimizations for that.
A clean-room JMS server typically provides a "native" implementation of
the pub/sub domain, without simply layering it atop point-to-point queue.
Some clean room JMS products even utilize IP multicast to broadcast JMS messages
over local area networks. This further increases the scalability.
This was first published in April 2002
