Configuring and scaling Web Apps no Azure - Part 1

In the previous article, we performed the implementation of our application in the web app template with App Service plan assigned and deployment being successfully done in Azure Portal. Now, we can make the necessary settings to adjust our application by taking the best PaaS model project that Microsoft Azure provides.

Using your credentials, log in to the Azure portal, access the resource group that we defined during the implementation of the application, called Packt, and finally click on webapp-packt.

In the central part of this screen, we have various options that we can use to run certain actions:

Browse: The web app will appear in your default browser.

Stop / Start: The web app will be stopped or started.

Swap: With this option, it is possible to make an exchange in the slots, providing a version of your application that has been approved from the environment of approval for production in an easy and fast way. You can understand the concept of the slot as an isolated container for your application to facilitate the process of developing an application, without the need to create another web app resource to validate an application, for example.

Restart: If you use this action, your application will be restarted.

Delete: If you perform this action, your web app will be deleted.

Get publish profile: If you perform this action, you will download the file with the necessary settings so that you can perform deploy using Visual Studio 2017, for example. The central idea of this option is to ease the process of configuring a solution created in Visual Studio and centralizing the publishing profile to be used by the developer team.

 Reset publish profile: If you perform this action, the credentials of the publication file will be reset.

Let's take a look at a few settings that you can use in your web app. The following options are part of the Deployment section.

Deployment slots are a feature of the Azure App Service. You can create different slots for your application (such as Dev, Test, or Stage). The production slot is where your application will be available to the user. Each slot created for an application will have a specific URL. The main purpose of working with slots is the ability to validate an application without affecting the release that is in production. After the validations happen without errors of the application, we simply change from the developer slot to the production slot so that the new version of our web app is available to the user.

To create a slot, choose Deployment slots in the Deployment section and then click Add Slot to add the new slot.

The first slot to be created will be used to a version of our web app that will have Development as the Source and Homologation as the Destination, so the Homologation team can validate the web app without worrying about any changes made by the development team until the sending of the web app for the homologation slot.

The second slot to be created is used to transfer the web app version validated by the approval team to the production environment.

Another interesting configuration that is available in the Deployment section, is the Deployment Center option. With Deployment Center, you can perform a process for configuring continuous integration / continuous deployment for your web app. Through a guided experience, so a configuration wizard, you'll have a centralized overview of all the deployment options available and you can select the repository you want for your web application. Note that different source controls can be used for your project in the development of your application.

It didn't end there. In the next article, we will complete this configuration of scale webapps. I hope I have helped you.