Why swap slots if I always want a production and staging version of my web app available?
Less downtime. Your new production will be live in the staging slot, then you swap slots and your new version is live quickly.
But what if I always want a staging and production slot available
Like my staging slot will host changes made from a stage branch
But I also want the production slot to be live as well
When you’ve switched them you have your staging slot again
So it is possible to have two slots available at both times?
What do you mean by available?
You have two slots, one of them is production at all times
But you can choose which one is production
Say I have myapp.domain.com and myapp-staging.domain.com I want myapp and myapp-staging to always be available at the same time. So that we can work on a myapp-staging without ever affecting myapp
Thanks for being patient. This whole Azure App slot is new to me.
The staging slot should have it’s own url AFAIK
Take a look at Blue Green Deployment strategy.
Thanks !
that’s a part of the Azure App Service?
It’s a deployment strategy, not a particular technology. Once you see how that works, the deployment slots with Azure Apps will make a little more sense, too.
Oh gotcha. Thanks 
Just disregard with the poor naming that MS uses for “production” and “staging” its not really the pure distinction of a prod or stg environment.
Instead think of it as 2 web apps. One with version 1.0 of your app and other with version 1.1. Both are your production environment. And now you want to make version 1.1 the active one that serves the clients. Thats what slots are. you swap slot 1.0 with slot 1.1/ MS calls it production slot and staging slot and gives each a DNS alias in the URL.
internally it swaps the DNS to point to the right version when you do the swap of the slots.
you can have a REAL staging environment where you also use 2 slots (the 1.0 called production slot and 1.1 called staging slot)
Thanks for clarifying.
