Instantiating multiple instance of Microsoft.Azure.ServiceBus.QueueClient in .NET Core

user_5044734 0
Viewed 1245

I'm looking for the best practices for creating multiple Microsoft.Azure.ServiceBus.QueueClient instances in .Net Core using Dependency Injection. Should instances be singleton, for example? I couldn't find any official guidance on this.

Currently I am resolving one instance as a singleton, but a new requirement has necessitated that I instantiate multiple QueueClient instances for different queues using the same connection string.

The concern is connection pooling and lifetime, and how this is/should be managed. I've found mentions of MessagingFactory in .NET Framework, but not much info about the equivalent (if any) in .NET Core.

.net-core-2.2 azureservicebus .net-core
1 Answers

.NET Framework version of the client was using MessagingFactoring as a mechanism for connection pooling. Each client created using the same factory would re-use the same connection object.

With .NET Standard client this is no longer the case. You get to choose wherever you want to pool the connection or not. If you construct all of your queue clients using a connection string, you will create new connections each time. It's both costly and requires resources. If you construct your queue clients using the same ServiceBusConnection object, then you'll re-use the same connection and will not pay the cost of re-establishing a connection each time.

Note that whenever you reuse the object, you need to verify that the underlying connection is still opened. If it's not, you will need to create a new one by specifying the connection string or instantiating a new connection object using the connection string you have.

user_595630
Related