How to deploy a site for production with minimal impact on users

Question

I am trying to find the best server architecture solution for deploying monthly updates on the Asp.net external public website. I am looking for ways to release a new version of the website with minimal impact on users. Besides deploying a standard method (for example, stopping IIS, copying a new website through an existing website, starting IIS), what are the “best” solutions for deploying there? It would be nice if they kept their session and were not supposed to see the message “Website under maintenance” during the update.

My server configuration

We have 2 IIS (2003) web servers and are trying to figure out how to use them for deployment. My first thought was to update an inactive web server with the latest version. Then, to gracefully point web traffic to this server with minimal impact on users (at best, the user will not lose the session). How would you decide to "reassign" web traffic from server 1 to server 2? Change NAT firewall? Changing DNS Records? Any other way? We should be able to test a live site immediately after the release of new changes (duh).

By the way, we use nant and cruise control to automate assemblies and a custom web service to deploy assemblies for production. Thus, all this is automated with the click of a button.

Can a better solution be achieved using a third server? If so, how?

Answer 1

How do we do it

We have a load balancer from netscaler,

Withdraw one web server from the loadbalancer, complete all deployments, run iisreset, and return it to the load balancer.

Do the same for server 2.

Finally, the loadbalancer cache is invalid.

Answer 2

Well, there are a couple of things:

• . Windows 2003 Windows (WLBS), . , , . , , .

• -, , . HTTP , , , , . ASP.NET Forms Authentication - cookie ASP.NET. , - , , - . .

, - . , , : , , , .

Answer 3

. , :

- ASP.NET ( , ), - , , OutOfProc ASP.NET.

, , , . -.

- , -, .

, , . .

, -, , OutOfProc SQL. , -. , .