Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

When two different application systems are connected via a Message Channel and they need to exchange information, then that data can be packaged into an agnostic object called a Message. This is a generic container of data and any object can be provided as the message payload. Therefore, any data that needs to be transmitted in a messaging system must be converted into a Message.

By encapsulating the data in a generic wrapper like Message object, the messaging system can pass it around without any knowledge of the data’s type. As an application evolves to support new types or when the types themselves are modified or extended, the messaging system is not affected.

The Message can contain the following information:

  • body - the message body (i.e. payload)

  • headers - headers with additional information

  • messageId - Unique id of the message.

  • timestamp - The timestamp of the message

  • No labels