If you need to ensure that your messages are delivered in the correct order in all circumstances, you can use one of the following strategies:
If a subscriber receives a publication message that is out of order, it can react in various ways:
In both of the above solutions, the publisher and subscriber need to remember information about the last message they processed for a particular stream and topic. In the first solution this is the SequenceNumber for the Publish message, and in the second solution it is the PublishTimestamp. This information might need to be remembered atomically with issuing or receiving a publication. This can be accomplished by saving the information on a queue, using the same unit-of-work as the one in which the publication is put or retrieved.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
amq622g |