Scribd
Upload
44 views10 pages

Message Communication

This document discusses message-oriented communication and middleware. It covers: - Synchronous vs asynchronous communication models and the advantages of asynchronous messaging. - Message queuing systems use message brokers and queues to provide asynchronous and persistent communication between applications. - IBM MQSeries is an example of message-oriented middleware that uses queues managed by queue managers to reliably transmit messages between applications even if the sending and receiving applications are not both active.

Uploaded by

iti1906
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
44 views10 pages

Message Communication

This document discusses message-oriented communication and middleware. It covers: - Synchronous vs asynchronous communication models and the advantages of asynchronous messaging. - Message queuing systems use message brokers and queues to provide asynchronous and persistent communication between applications. - IBM MQSeries is an example of message-oriented middleware that uses queues managed by queue managers to reliably transmit messages between applications even if the sending and receiving applications are not both active.

Uploaded by

iti1906
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 10

Message-Oriented

Communication

• Synchronous versus asynchronous communications

• Message-Queuing System

• Message Brokers

• Example: IBM MQSeries

02 – 26 Communication/2.4 Message-Oriented Communication


Synchronous Communication

Some observations: Client/Server computing is generally based on a


model of synchronous communication:
• Client and server have to be active at the time of communication
• Client issues request and blocks until it receives reply
• Server essentially waits only for incoming requests, and
subsequently processes them

Drawbacks of synchronous communication:


• Client cannot do any other work while waiting for reply
• Failures have to be dealt with immediately (the client is waiting)
• In many cases the model is simply not appropriate (mail, news)

02 – 27 Communication/2.4 Message-Oriented Communication


Asynchronous Communication: Messaging
Message-oriented middleware: Aims at high-level
asynchronous communication:
– Processes send each other messages, which are queued
– Sender need not wait for immediate reply, but can do other things
– Middleware often ensures fault tolerance

02 – 28 Communication/2.4 Message-Oriented Communication


Persistent vs. Transient
Communication

Persistent communication: A message is stored at a


communication server as long as it takes to deliver it at the
receiver.

Transient communication: A message is discarded by a


communication server as soon as it cannot be delivered at the
next server, or at the receiver.

02 – 29 Communication/2.4 Message-Oriented Communication


Messaging Combinations

02 – 30 Communication/2.4 Message-Oriented Communication


Message-Oriented Middleware

Essence: Asynchronous persistent communication through


support of middleware-level queues. Queues correspond to
buffers at communication servers.

Canonical example: IBM MQSeries

02 – 31 Communication/2.4 Message-Oriented Communication


IBM MQSeries (1/3)

Basic concepts:
• Application-specific messages are put into, and removed from
queues
• Queues always reside under the regime of a queue manager
• Processes can put messages only in local queues, or through an
RPC mechanism

Message transfer:
• Messages are transferred between queues
• Message transfer between queues at different processes, requires
a channel
• At each endpoint of channel is a message channel agent (MCA)
– Setting up channels using lower-level network communication
facilities (e.g., TCP/IP)
– (Un)wrapping messages from/in transport-level packets
– Sending/receiving packets

02 – 32 Communication/2.4 Message-Oriented Communication


IBM MQSeries (2/3)

• Channels are inherently unidirectional


• MQSeries provides mechanisms to automatically start MCAs
when messages arrive, or to have a receiver set up a channel
• Any network of queue managers can be created; routes are set
up manually (system administration)

02 – 33 Communication/2.4 Message-Oriented Communication


IBM MQSeries (3/3)
Routing: By using logical names, in combination with name resolution
to local queues, it is possible to put a message in a remote queue

Question: What’s a major problem here?


02 – 34 Communication/2.4 Message-Oriented Communication
Message Broker
Observation: Message queuing systems assume a common messaging
protocol: all applications agree on message format (i.e., structure and
data representation)
Message broker: Centralized component that takes care of application
heterogeneity in a message-queuing system:
• Transforms incoming messages to target format, possibly using
intermediate representation
• May provide subject-based routing capabilities
• Acts very much like an application gateway

02 – 35 Communication/2.4 Message-Oriented Communication

You might also like