1 / 14

Asynchronous Communication Between Components

Asynchronous Communication Between Components. Presented By: Sachin Singh. Characteristics of Synchronous Communication. The remote object must currently be alive. The client must establish a connection to the object.

rigel-burris
Télécharger la présentation

Asynchronous Communication Between Components

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Asynchronous Communication Between Components Presented By: Sachin Singh

  2. Characteristics of Synchronous Communication • The remote object must currently be alive. • The client must establish a connection to the object. • The client must invoke a method on the object, and wait while the remote object executes the method and returns the result, if any.

  3. Real Life Business Applications • Applications distributed across heterogeneous platforms over the network • Networks/Components prone to failure • Dynamic Business needs- scalable architecture • Requirement  “Loose Coupling”

  4. Message Oriented Middleware • Rather than connecting directly to a remote object, the client connects to the message-oriented middleware and sends its message. • MOM middleware is an event-driven, asynchronous, non-blocking and message-based communication method that guarantees message delivery.

  5. Quote • Every DAD needs a MOM. --The Message Oriented Middleware Consortium Interpretation? ? ? Every Distributed Application Development needs a Message-Oriented Middleware.

  6. MOM Products • MSMQ (Microsoft Message Queuing) • IBM MQSeries • JMS (Java Message Services)

  7. MOM Typical Architecture

  8. The JMS Case • The Java Message Service (JMS) provides a standard Java-based interface to the message services of a MOM of some other provider.

  9. JMS Characteristics • Messaging • loosely coupled communication • sender/receiver do not have to be active at the same time • Sender/receiver only have to agree on message format • Applications • no dependency on interfaces • components which may be disconnected (e.g. mobile phones)

  10. JMS API Architecture • A JMS provider is a messaging system that implements the JMS interfaces and provides administrative and control features. J2EE platform release 1.3 • JMS clients are the programs or components, written in the Java programming language, that produce and consume messages. • Messages are the objects that communicate information between JMS clients. • Administered objects are pre configured JMS objects created by an administrator for the use of clients. (Ex destinations and connection factories)

  11. JMS – Publish/Subscribe Messaging Domain

  12. Advantages • High-level abstraction • physical location/ physical details hidden • Interoperability • Portability • Flexibility • Scalability • Reduces complexity

  13. Disadvantages • Implementations are proprietary • Component can overwhelm other component

  14. Thank You !!

More Related