SzymonPobiega / NServiceBus.Bridge

A bridge that can connect endpoints using different NServiceBus transports
MIT License
4 stars 3 forks source link

Production readiness #4

Open antongeorgiev opened 7 years ago

antongeorgiev commented 7 years ago

There is a great potential in this project but in order to be considered production-ready it needs to address certain operational concerns .

We are evaluating the Bridge for our scenario where we have endpoints configured with either MSMQ or AzureServiceBus transports and it looks perfect for our needs. However there doesn't seem to be enough documentation yet on certain configuration aspects like:

Thanks and keep up the good work!

SzymonPobiega commented 7 years ago

Hi @antongeorgiev

Thanks for the feedback and the kind words. Let me try to address some of your comments

Hosting

We recommend using something similar to https://github.com/Particular/NServiceBus.Bootstrap.WindowsService for hosting. Unfortunately with the .NET changes the old source-only packages are broken (you can't edit files from source-only packages) and dotnet-new templating is not production-ready just yet

Logging

I've created a separate issue for the logging as I admit I haven't verified it thoroughly

Perf counters

As we announced recently, Particular is working on a streamlined monitoring experience for the whole platform. This new thing will replace and extend the old Perf Counter support built-into NServiceBus. Once that new monitoring infrastructure is out I'll hook up a bridge to it so that it is properly monitored

Perf tuning

Performance tuning is transport-specific. The bridge just utilized whatever each transport has to offer and allows customizing it. Please see the doco for a specific transport to learn more. Some transports, like ASB, have quite a lot of options allowing fine-tuning. Others, like MSMQ, have basically no options at all.