Home/ Questions/Q 690003
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T02:23:27+00:00

So it’s easy to load balance an ASP.NET web application. You set up a

  • 0

So it’s easy to load balance an ASP.NET web application. You set up a load balancer between two servers, and if the web server isn’t responding on Port 80, it won’t receive requests.

Are there any proven techniques for doing this for a C# console application or Windows service that takes actions of its own volition? Are there any frameworks for knowing if peer processes are alive or dead, doing heartbeats, etc?

I’ve been experimenting a bit with NServiceBus and it seems like, for certain kinds of applications, it would help to have most of the work done as a response to an event, which makes it more like a web application, actually, and therefore easier to scale and load balance with multiple processes, but I feel like that’s a half-baked solution since in most cases there usually needs to be some concept of a “master” process that’s responsible for getting work started.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    NServiceBus does indeed handle this for you with its Distributor process (described here: http://docs.particular.net/nservicebus/scalability-and-ha/distributor/). The generic host that comes with NServiceBus allows you to have the exact same code and configuration run both as a console app and as a windows service (described here: http://docs.particular.net/nservicebus/hosting/nservicebus-host/).

    You can have this for events as well as for regular command messages.

    If you want a “master” process to decide what to do when all the load-balanced work completes, that is provided to you in the form of the saga infrastructure (described here: http://docs.particular.net/nservicebus/sagas/ and demonstrated in the Manufacturing sample that comes with NServiceBus).

    In short, you should pretty much be covered.

    • 0