Queued Messaging

With queued messaging, senders and receivers of data do not know about each other but are connected by a channel, a queue or a topic. The data is encapsulated as a message for transmission via the messaging system. A channel transmits a message using store-and-forward, such that the message is always stored somewhere and won't be lost (within the boundaries of the channel's quality of service). Because messages are always stored, they queue-up within the channel until they are consumed by the receiver.

See Basic Messaging Terminology.

Also see my blog posting Interoperable Queued Messaging, based on the blog posting Making Loose Coupling Real: The Need for Interoperable Queued Messaging by David Chappell.

Technologies

This topic includes technologies like:

• JMS
  • WebSphere MQ
  • WAS SIBus
• MSMQ
• WS-ReliableMessaging
• WS-Notification
• Reliable Asynchronous Messaging Profile (RAMP)
• Web Services Reliable Exchange (WS-RX)

Resources

Enterprise Integration Patterns is an especially good book on how to design application integration solutions using queued messaging.

Issues

Here are some common issues and problems with messaging:

• Message Order