Multiple applications in an Azure web app

2
votes

I have an Web API service currently sitting on an Azure Web app. It's used by mobile apps and have been thinking about how to do versioning as people might be using different version of the mobile app.

I've decided to do v1, v2 etc as different apps, so that when I move on to a new version I effectively freeze the previous version and not have to touch it at all.

One way of doing this is to create an sub application in my Azure Web App for each version, but have a few questions regarding this:

  1. Do all apps within a Web App share the same app pool? If I deploy one using Team Services will it restart all the applications?
  2. Is there just the one shared app config for all applications within in Web App? Using IIS each application would have it's own web.config but not sure if this is the case with Azure.
  3. Not really a question, but in case anyone else was thinking of this route. By using applications for different versions means I won't be able to use slots unless I deploy every version each time, which I don't want to do.

Thanks

2
azureazure-web-app-service

2 Answers

1
votes

Do all apps within a Web App share the same app pool?

As far as I know, in Web Apps, each site and its child applications run in the same application pool. We could find detailed info at this article .

Is there just the one shared app config for all applications within in Web App? Using IIS each application would have it's own web.config but not sure if this is the case with Azure.

The application runs in its own directory with its own web.config. We could find the web.config files under each application directory via Kudu console or App Service Editor.

enter image description here

1
votes
  1. They do not.
  2. They have separate.
  3. I don't seem to understand the question. I believe you could upload different versions on the same app to different slots

"It's important to emphasize that the slot is in itself a regular Azure Web App, it will have its own app settings, connection string, any other configuration settings and even an scm site (https://mysite-staging.scm.azurewebsites.net).

In fact by default each Azure Web App has a single deployment slot called production which is the Azure Web App itself."

http://blog.amitapple.com/post/2014/11/azure-websites-slots/#.WCLqF_mcFEY