search

herecydev / Rush

Messaging library for .NET
MIT License
2 stars 0 forks source link

Provider Extensions #9

Open smudge202 opened 8 years ago

smudge202 commented 8 years ago

I was just perusing the features/azure branch and thought I'd make some observations.

Just for consideration, but oftentimes libraries like these rely on provider mechanisms such as with MS Logging, Serilogger, and I'm sure there are dozens of more examples that I can't think of off the top of my head.

Point being, should the Azure implementation be added as an IServiceCollection extension, or through some kind of provider mechanism on the existing/core IServiceCollection extension?

(The same would hold true for the InMemory version ).

herecydev commented 8 years ago

Frankly, I'm not sure yet. I like the concept that each project brings in an extension just like Aspnet's logging and I think I mirror that behaviour. However if I start to run into issues then I can change to a provider-focused design. It's hard to see the immediate benefits but I'm more than flexible to give it a try.