An application is receiving messages on a Publish-Subscribe Channel.
How can a subscriber avoid missing messages while it’s not listening for them?
Use a Durable Subscriber to make the messaging system save messages published while the subscriber is disconnected.
A durable subscription saves messages for an inactive subscriber and deliveres these saved messages when the subscriber reconnects. In this way, a subscriber will not loose any messages even though it disconnected. A durable subscription has no effect on the behavior of the subscriber or the messaging system while the subscriber is active (e.g., connected). A connected subscriber acts the same whether its subscription is durable or non-durable. The difference is in how the messaging system behaves when the subscriber is disconnected....
Related patterns: Guaranteed Delivery, Message Expiration, Point-to-Point Channel, Publish-Subscribe Channel
Find the full description of this pattern in:|
Enterprise Integration Patterns
Gregor Hohpe and Bobby Woolf
Parts of this page are available under
the Creative Commons Attribution license.
You can reuse the pattern icon, the pattern name, the problem and solution statements (in bold), and the sketch
under this license. Other portions of the text, such as text chapters or the full pattern text, are protected