A Message channel is a basic architectural pattern of a messaging system and is used fundamentally for exchanging data between applications. While an application maybe unaware of other applications that may receive the data, by picking a particular channel, it makes the An application can use a channel to make a specific type of data available to any receiver application applications that wishes need to consume a particular that type of data transmitted through a given channel.
This chapter introduces different types of channels used in a messaging system, their behaviors, and how each of them can be simulated using tthe WSO2 ESB.
 | 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. | ||||
 | 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. | ||||
 | How multiple messaging systems can be connected so that messages available on one are also available on the others. | ||||
 | 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. |
| Excerpt | ||
|---|---|---|
| ||
Messaging Channels, Integration Patterns with WSO2 ESB |