JMS is the Message Oriented Middleware (MOM) from J2EE platform that facilitates the asynchronous distributed communication between software components and applications. Alternatively, JMS provides the decoupled interface for exchanging information between software components and applications. The software components and applications may or may not be build in J2EE.

JMS supports the following two models for message delivery.

• Point-to-Point (Queue)
• Publish and Subscribe (Topic)

Misc JMS Terms

• Provider: An implementation of the JMS interface for a Message Oriented Middleware(MOM) acts as Message Store.
• Client: An application or process that produces and/or consumes messages.
• Producer: A JMS client that posts messages into the Message Store.
• Consumer: A JMS client that receives messages from the Message Store.
• Message: An object that contains the data being transferred between JMS clients.
• Queue: Message is consumed only once by a JMS client from the Message Store.
• Topic: Message could be consumed by multiple JMS client from the Message Store.

Enterprise class MOMs providers are expected to scale, highly available, ensure message delivery, and support client application(s) for multiple platforms and technologies.

Disclaimer

The thoughts expressed in the blog are those of the author and do not represent necessarily the official policy or position of any other agency, organization, employer, or company. Assumptions made in the study are not reflective of the point of view(s) of any entity other than the author. Since we are critically thinking human beings, the point of view(s) is always subject to change, revision and rethinking at any time. While reasonable efforts have been made to obtain accurate information, the author makes no warranty, expressed or implied as to its accuracy.