The content in this documentation is for older versions of WSO2 products. For updated information on Enterprise Integration Patterns, go to the latest Micro Integrator documentation. "> The content in this documentation is for older versions of WSO2 products. For updated information on Enterprise Integration Patterns, go to the latest Micro Integrator documentation.

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 13 Current »

A Message channel is a basic architectural pattern of a messaging system and is used fundamentally for exchanging data between applications. An application can use a channel to make a specific type of data available to any receiver applications that need to consume that type of data.

This chapter introduces different types of channels used in a messaging system, their behaviors, and how each of them can be simulated using WSO2 ESB.

Point-to-Point Channel

How the caller can be sure that exactly one receiver will receive the document or perform the call.


How the sender broadcasts an event to all interested receivers.


How the application sends a data item such that the receiver will know how to process it.

Invalid Message Channel

How a messaging receiver gracefully handles a message that makes no sense.

What the messaging system does with a message it cannot deliver.

How the sender ensures delivery of a message, even if the messaging system fails.

How to connect an application to the messaging system to send/receive messages.

Messaging Bridge

How multiple messaging systems can be connected so that messages available on one are also available on the others.

Message Bus

An architecture enabling separate applications to work together in a decoupled fashion such that applications can be easily added or removed without affecting the others.

  • No labels