The impact of losing messages
If you are planning to use the HTTP POST action, please bear in mind that this is different from a Request/Response action in that HTTP POST sends the message but does not read the output (it operates on the fire and forget principle). Therefore, if you are sending to a resource that could be busy, will the message be actioned? If the resource is turned off, do you have a mechanism to be able to rerun the message at a later point? Here, setting the retry policy to the default (four tries) when sending a Web API message that inserts a record into a database would not be a good idea as the HTTP call could be sent four times. The record you are trying to add will effectively be added to the database four times!
For this reason, when using HTTP calls to keep systems in sync, I always set Retry Policy to None:
Therefore, by setting the policy to none, we can avoid additional and unwanted...