[FIXED] How to handle Azure web app versioning?

Issue

I am about to develop a new website (SaaS) project and want to use Azure as the platform. I want every clients data to be isolated from each other which i chose to achieve by using elastic database engine.

Each client must have a specific endpoint like bla.siteName.com, bla2.siteName.com, bla3.siteName.com this is easily achieved by subsomains and usage of custom domains.

And finally website itself should be hosted on azure web app but here is where i hit a wall.

I want to be able to move each client at a time to the newer version of the web application.

So if My web app is runing version 1.0, and i add a new feature in version 1.1, i want to be able to move client and clients db to version 1.1 without them noticing it.

So far my thought is to publish new web app version 1.1 and move subdomain name of that specific client to version 1.1 web app. But this will end up in downtime, because switch of subdomains take time.

Am i missing something or am i just about to overengineer something that is very simple?

Or should i just focus on single website serve all approach, and just upgrade all clients databases at once?

Solution

You may want to try Azure Deployment Slots. It has many uses, including the one you describe. You can use Azure Traffic Routing to route a subset of your users to one of your deployment slots.

Answered By - Randy Minder

Answer Checked By - Willingham (PHPFixing Volunteer)