We wanted some guidance on making it easier for us to upgrade our site.
We have an application that users use continually for 3+ hours. It is used for studying so we have use at all times of day. So if we have an application update that will or could potentially break their experience, we have to plan an outage and customers complain.
This is how we'd like to handle it:
- We launch another Azure website with our updated application
- Something happens to let a load balance or application gateway or something know the new version is online and traffic is changed based on that
- Current users continue to go to the past version of the application on on Azure website (cookie or ip affinity)
- New users will now go to the new version of our application
So basically its load balancing the old server with a weight of 0 except for users with affinity (either cookie or IP).
Is there a way to handle this situation using Azure services? We were hoping Application Gateway could do this but it only supports round-robin rule currently.
Thank you for your help