Thus, it is easy to load the balance of an ASP.NET web application. You set load balancing between the two servers, and if the web server does not respond to port 80, it will not receive requests.
Are there any proven methods for doing this for a C # console application or a Windows service that does the action of its own accord? Is there any framework for knowing whether peer processes are alive or dead, make heart contractions, etc.?
I experimented a bit with NServiceBus , and it seems that for some kinds of applications this would help most of the work done in response to the event, which makes it more like a web application, and therefore it is easier to scale and balance the balance with several processes. but I feel that this is a half-baked solution, because in most cases there usually should be some kind of concept of the "main" process responsible for starting the work.
source
share