Messaging Channels

Channel Adapter

Use a Channel Adapter that can access the application's API or data and publish messages on a channel based on this data, and that likewise can receive messages and invoke functionality inside the application.

Datatype Channel

Use a separate Datatype Channel for each data type, so that all data on a particular channel is of the same type.

Dead Letter Channel

When a messaging system determines that it cannot or should not deliver a message, it may elect to move the message to a Dead Letter Channel.

Guaranteed Delivery

Use Guaranteed Delivery to make messages persistent so that they are not lost even if the messaging system crashes.

Invalid Message Channel

he receiver should move the improper message to an Invalid Message Channel, a special channel for messages that could not be processed by their receivers.

Message Bus

Structure the connecting middleware between these applications as a Message Bus that enables them to work together using messaging.

Message Channel

Connect the applications using a Message Channel, where one application writes information to the channel and the other one reads that information from the channel.

Messaging Bridge

Use a Messaging Bridge, a connection between messaging systems, to replicate messages between systems.

Point-to-Point Channel

Send the message on a Point-to-Point Channel, which ensures that only one receiver will receive a particular message.

Publish-Subscribe Channel

Send the event on a Publish-Subscribe Channel, which delivers a copy of a particular event to each receiver.