Additionally, there is an App Service Plan (ASP) called STICKYSLOT-ASP that runs an Azure App Service Web App called stickyslot with a deployment slot named testing.

Notice in Figure 1 there is a SQL Server which has 2 SQL Azure databases on it, one called stickyslot-pro and the other stickyslot-tst. The beauty of the deployment slot is that you can slick a button and the deployment slot which contains the new version is swapped with the production, and bang, the new version is live, with just a click. This development slot lets you deploy you test or non-production ready code for testing prior to the release to the live Web App. A deployment slot is an additional Azure App Service Web App instance (W3WP) which is ~bound to your production Azure App Service Web App of the same name and runs on the same App Service Plan (ASP) that I discuss here. When you make a deployment you would not want to take the risk of deploying bugs or having significant downtime when you deploy a new release, this is what you would want to have a Deployment Slot.

Consider you have an Azure App Service Web App that handles a large amount of traffic and accesses a database, with an architecture similar to that shown in Figure 1.