Handling Skipped (Deadletter messages) in Masstransit/Azure Service bus
The scenarion we want to protect us from is when deploying several services (microservices application) and a new messages (MessageA) are part of the release. The service that publish the MessageA are deployed before the services that consume MessageA.
Azure Service Bus seems to use HTTP long polling instead of AMQP
In our application, we use MassTransit and Azure Service Bus. Configuration code looks like this:
MaxConcurrentCalls on Azure Service bus using masstransit
Based on the Masstrainsit documentation MaxConcurrentCalls means this.