: How to make live site updates without affecting users? My company has an e-commerce website which I constantly keep updating the website for. The problem is whenever I push out some stuff

@BetL925

I use load balancing to prevent errors and keep the site up during updates. For this to work you need at least two servers behind a load balancer that sends traffic to whichever server is up. My procedure for updating my sites is:


Tell "Server A" to start serving an error page at the URL that the load balancer pings. This tells the load balancer to stop sending traffic to this server.
Wait 30 seconds or so until traffic stops hitting the server.
Update the code on this server.
Tell the server to stop serving an error page at the ping URL.
Wait until that server is getting traffic again.
Repeat steps 1-5 with "Server B".

Vote Up Vote Down

@Nimeshi995

Specific to your IIS environment:

You could consider creating a new application pool for your changes, as covered here:


The element contains configuration settings for all
application pools running on your Internet Information Services (IIS)
7 server. An application pool defines a group of one or more worker
processes, configured with common settings that serve requests to one
or more applications that are assigned to that application pool.
Because application pools allow a set of Web applications to share one
or more similarly configured worker processes, they provide a
convenient way to isolate a set of Web applications from other Web
applications on the server computer. Process boundaries separate each
worker process; therefore, application problems in one application
pool do not affect Web sites or applications in other application
pools. Application pools significantly increase both the reliability
and manageability of your Web infrastructure.


And then remove the older application pool at a later time to increase server performance.

Vote Up Vote Down

@Pope3001725

Don't deploy when the site is live. You should take down the site so no users are active at the time of deployment. If your site is very active advanced notice of downtime is usually encouraged. Also, when the site is down, be sure to have a notice up stating why the site is down and when it is expected to be back up.
Don't deploy during active periods of site usage. Deployments should occur late at night when site usage is at a minimum. No one likes to work after hours but this is part of how code rollouts work.

Vote Up Vote Down