Enterprise Integration Patterns
Messaging Patterns
Messaging Patterns
MessageMessageMessaging Patterns » Messaging Systems

An enterprise has two separate applications that are communicating via Messaging, using a Message Channel that connects them.

How can two applications connected by a message channel exchange a piece of information?

Package the information into a Message, a data record that the messaging system can transmit through a message channel.

Thus any data that is to be transmitted via a messaging system must be converted into one or more messages that can be sent through messaging channels.

A message consists of two basic parts:

  1. Header – Information used by the messaging system that describes the data being transmitted, its origin, its destination, and so on.
  2. Body – The data being transmitted; generally ignored by the messaging system and simply transmitted as-is.

... Read the entire pattern in the book Enterprise Integration Patterns

Related patterns:

Canonical Data Model, Command Message, Document Message, Event Message, Message Channel, Message Expiration, Message Sequence, Messaging, Request-Reply

Creative Commons Attribution License

You can reuse the following elements under the Creative Commons Attribution license: pattern icon, pattern name, problem and solution statements (in bold), and the sketch. Other portions are protected by copyright.

Enterprise Integration Patterns book cover

Enterprise Integration Patterns
The classic, as relevant as ever. Over 90,000 copies sold.

Software Architect Elevator book cover

The Software Architect Elevator
Learn how architects can play a critical role in IT transformation by applying their technical, communication, and organizational skills.

Cloud Strategy book cover

Cloud Strategy
Fill the large gap between high-level goals and product details by understanding decision trade-offs.