Staging and Production IIS Division

Question

I’m learning how to integrate the staging environment on our IIS server, where you can warm up the application before replacing it with a working environment.

The only real solution I can find is:

• Change directory settings

  • Which seems like a slow process to me because IIS will have to compile and unfreeze the new directory after the exchange. (I guess this is correct?)

• They have two sites and replace the bindings after the setting has been warmed up.

• The presence of a load balancer and the exchange between the two sites. It just seems redundant as both sites will be on the same server.

The first two scenarios seem to be hacked and error prone.

Obviously, there must be something I'm missing. Therefore, I appeal to you, experts!

Ps. We are on Windows Server 2012, IIS v8.0

Answer 1

Options 1 and 2 will cause the iis application pool to be recycled. This may or may not be a big deal, depending on the type of business you are launching, how you process sessions, etc.

Option 3 looks like a more elegant option and gives you some flexibility if you ever want to scale and add additional machines. And it’s easier to explain to future developers already familiar with the template.

http://martinfowler.com/bliki/BlueGreenDeployment.html

Powershell - , , .