Why Should BlobStorageService Be Registered as Singleton

[markgmarkg]

Hi Daniel,

Quick "lifetime" question...
I perfectly understand why BlobServiceClient should be a singleton - it's MS guidance.
services.AddSingleton(factory => new BlobServiceClient(storageConfiguration.ConnectionString));

I'm wondering what is a reason to register BlobStorageService as singleton.
services.AddSingleton<IBlobStorageService, BlobStorageService>();

Thank you,
mg

[Daniel-Krzyczkowski]

Hi Mark,

Thank you - good question.
There reason why I decided to register BlobStorageService as singleton is the fact that it does not use any other dependencies than BlobServiceClient which is also registered as singleton. As BlobServiceClient manages connections internally (as explained by Microsoft) I did not see any reasons to register BlobStorageService as transient or scoped.
Please let me know if it make sense.

[markgmarkg]

Hi Daniel,

Thank you for such a quick response :)
I would choose non-singleton scope only for one reason - singletons require some kind of synchronization...
Blob operations may be lengthy, although no state really managed in BlobStorageService

Regards,
Mark

[Daniel-Krzyczkowski]

Hi Mark,

This is interesting suggestion, thank you - I will be 100% honest with you. I did deep-dived into details but I assumed that if my class is using only this one singleton instance (BlobServiceClient) I assumed that there is no sense to register it in other way. I did not found any cons around this. I do not say that my solution is the only one and perfect. :)