Explain Java Message System

By Author: priya
Total Articles: 1
Comment this article

Java Message System :

In this article, the main focus will be on Message Orientated Middleware (MOM) and how it is implied in JE by JMS. There are other topics to be covered like Publisher, sender, destination, topic, queue and subscriber or receiver etc.
Data Access Layer :
In Java's EE application architecture there are technologies in the data access layer that talk with data stores like Java Persistence API, Java Connector Architecture that links your application to enterprise information systems (EIS); and Java Message Service (JMS).

Explain the use of JMS :
For passing the message in a loosely coupled fashion, scalable, asynchronous and secure manner among applications that are distributed is what JMS is used for. Sending and receiving of application messages through the Message Orientated Middleware using destinations. There are no means to interact at the same time by both sender and receiver and this is what asynchronous means.

The senders and the receivers are not aware of each other because of loosely coupled nature. In response to application load the different parts of the ...
... system can develop at different rates. Robustness in the system is offered by the system which otherwise has the tough times in handling the application start and behaving badly or stop working together.

Right time to Use JMS :

The right time to use JMS relies on the use case but usually it will fall into at least one of these use cases.
1) The first use case is this: a message should be sent by the application without needing an immediate response to that message. It might not be mandatory to respond the message and the application can continue its proper function without the response.

2) The sender does not depend on the interface of the receiver so there is no replacement that can be done by the receiver. For decoupling the application this comes down to a requirement for parts.

When the receiver is down the application should continue to run and the receiver can be broken and the application will resume its normal operation. Thus robustness is supported.