Use an injected Azure Service Bus client instead of initiating them ourselves
stijnmoreels opened this issue · 2 comments
Is your feature request related to a problem? Please describe.
Instead of doing the initiation and managing of our own Azure Service Bus client, we could rely on the built-in Azure Service Bus client extensions and let the developer be fully in control on how to handle the Azure Service Bus interaction.
Describe the solution you'd like
Use the built-in Azure Service Bus client to retrieve messages from Azure Service Bus. This will also mean that we will not have to do dispose the client but start/stop in case the message pump is restarted.
Additional context
https://docs.microsoft.com/en-us/dotnet/api/overview/azure/messaging.servicebus-readme-pre
Still have to figure some things out, if it's even possible for us to do this, but we should also consider the consequences because being dependent on this client will make the message pump registration maybe more obscure as there is now visible reference anymore to which Azure Service Bus the message pump would be consuming messages, it would only contain the name of the Azure client.
Closing as there is at the moment no real need.