ASP.Net zero down time deployment, which is better and cheaper?

Question

ASP.NET

Good afternoon, dear colleagues, I have been sleeping badly for a long time because I am tormented by one problem, its essence is as follows:
There is an ASP.Net MVC WEB API and an IIS7 application that processes requests from users. Actually, the problem is that from time to time you have to update the application, and at that moment the application pool is cleared and the application
becomes unavailable for 40-80s.
had to develop medium and large projects.
For myself, I’m still thinking of making two application pools on one machine, and in front of the server, raise Nginx as a reverse-proxy, in which it needs to manually manage which of the pools it needs to knock on. In this case, the update of the solution simply happens on the neighboring pool, and then the active pool in Nginx is switched. In the future, if the load grows, in theory it can be spread over different servers.
However, maybe I am reinventing the wheel and there are much simpler and cheaper solutions?
PS: The issue of price also matters. everything is in the cloud.

Answer 1

There is a solution using the Application Request Routing module, described on serverfault , however, I have not personally tried it. You can try to start with this, and if it doesn’t work reliably or if the load increases, then install nginx.