JMS is the producer and consumer model. Consumers are responsible for messages generated by consumer producers. JMS can be done in the background of asynchronous operations, applied to the specific work, it is useful to send internal messages, e-mail, texting, big operation in the background to do asynchronous operations.
The Java Messaging Service (Java message SERVICE,JMS) application interface is an API for message-oriented middleware (MOM) in the Java platform for sending messages between two applications, or distributed systems, for asynchronous communication. The Java messaging Service is a platform-agnostic API, and the vast majority of MOM providers support JMS. The specification for the Java messaging service consists of two message patterns, point-to-point and publisher / Subscriber. Many providers support this universal framework therefore, programmers can implement message-oriented operations in their distributed software, which will have different portability for message-oriented middleware products. The Java messaging service supports synchronous and asynchronous message processing, where asynchronous messages are necessary in some scenarios, and in other scenarios, asynchronous messages are more convenient than synchronous message operations. The Java messaging Service supports the event-oriented approach to receiving messages, and event-driven programming is now widely considered a productive programming paradigm that programmers are quite familiar with. In the application development, the Java message service can defer the choice facing the message middleware product, but also can switch in the different face message middleware.
The role of JMS