Best view in Firefox and Chrome

Asynchronous Messaging and JMS

Thursday, September 10, 2009
Convert Article to PDFPrint ArticleEmail Article to FrinedBookmark this Article

Have you ever work with the Asynchronous Java Messaging? Do you have any experienced with the beauty of the Asynchronous Messaging? Its very cool. Nowadays I'm working with the SpringJMS in the Athiva system. The Java Message Service (JMS) is a standard API for asynchronous messaging.
The Spring simplifies sending and receiving messages with JMS. In addition to basic sending and receiving of messages, Spring support the message-driven POJOs, a way to receive messages that resembles EJB’s message-driven beans (MDBs).

What is Asynchronous communication? How these Asynchronous communication offers through JMS? In this Article I'm going explain about the Asynchronous communication and about the JMS.

Its a simple concept. Yesh If the communication is synchronous, The client need to synchronous with the server or with the service provider. The client must wait for the service to complete and need to suspense its process until its get the responses from the server. But in the Asynchronous communication is a no-wait for the communication. Its mean, client and server are processing in Asynchronous manner. There is no interdependent in between the services and client. This is a very powerful concept in messaging.And when we come to JMS, it play a major role in Asynchronous communication. When one application sends information to another through JMS, there is no direct link between the two applications. Instead, the sending application places the message in the hands of a service that will ensure delivery to the receiving application. This is pretty cool, isn't it. The sender application don't need to worry about the other applications.

There are two main concepts in JMS: message brokers and destinations.

When an application sends a message, it hands it off to a message broker. A message broker is JMS’s answer to the post office. The message broker will ensure that the message is delivered to the specified destination, leaving the sender free to go about other business.

In JMS, there are two types of destination: queues and topics. Each of these is associated with a specific messaging model, either point-to-point (for queues) or publish-subscribe (for topics).

Here I gave a small introduction about the Asynchronous communication and the JMS. In my next Article I'll guide you to create a small messaging environment with the SpringJMS. Enjoy..

Read these Articles :


Anonymous said...

Amiable dispatch and this post helped me alot in my college assignement. Gratefulness you seeking your information.

Anonymous said...

Very Interesting!
Thank You!

Why Breeze

This is a new technological rhythm in the web. It blooms like a Breeze in your technological face with more than 75 technoligical atricles and guidences.

Contact Me
Contact Me Send an Email Facebook Account LinkedIn profile Twitter/Shayanth
Share And Save
Social Share with Twitter Facebook Share Add to Google Save on Delicious
Get Updates

The RSS will facilitate you to get the updates from Breeze. Click Here to redirect to the RSS link.

Designed by Posicionamiento Web | Bloggerized by GosuBlogger | Blue Business Blogger | Customized by SHAUOM