Hey all,
I have a subscription set to listen for messages that are dropped to a remote MSMQ via a web service as the publishing adapter. I do not control the adapter, however, I do work well with the developer and we've come across a unique challenge that I'm not fully sure how to overcome.
When his application finalizes a processes, the application is supposed to kick out one or two separate messages, although tied to a matching identifier, they are not always sent in the correct order that my integration requires. That alone, offers a possible convoy solution on my end, but the application is not guaranteed to send two messages based on a certain scenario. So…..I'm looking at either one of the two paths here…1) help adjust the adapter so that he can guarantee that he delivers the messages in sequential order from an asynchronous web service solution…or 2) build a new orchestration solution that performs a correlation on his messages but is flexible enough to know that I may never get a second message if the right scenario is hit…problem is that I will not know if I am to expect one message or two based on the data in the messages.
Warning: I may be overthinking this already, so feel free to cyber-slap me if so desired.
Thoughts?
-Rich