Book Image

A Developer's Guide to Cloud Apps Using Microsoft Azure

By : Hamida Rebai Trabelsi
Book Image

A Developer's Guide to Cloud Apps Using Microsoft Azure

By: Hamida Rebai Trabelsi

Overview of this book

Companies face several challenges during cloud adoption, with developers and architects needing to migrate legacy applications and build cloud-oriented applications using Azure-based technologies in different environments. A Developer’s Guide to Cloud Apps Using Microsoft Azure helps you learn how to migrate old apps to Azure using the Cloud Adoption Framework and presents use cases, as well as build market-ready secure and reliable applications. The book begins by introducing you to the benefits of moving legacy apps to the cloud and modernizing existing ones using a set of new technologies and approaches. You’ll then learn how to use technologies and patterns to build cloud-oriented applications. This app development book takes you on a journey through three major services in Azure, namely Azure Container Registry, Azure Container Instances, and Azure Kubernetes Service, which will help you build and deploy an application based on microservices. Finally, you’ll be able to implement continuous integration and deployment in Azure to fully automate the software delivery process, including the build and release processes. By the end of this book, you’ll be able to perform application migration assessment and planning, select the right Azure services, and create and implement a new cloud-oriented application using Azure containers and orchestrators.
Table of Contents (20 chapters)
1
Part 1 – Migrating Applications to Azure
6
Part 2 – Building Cloud-Oriented Applications Using Patterns and Technologies in Azure
10
Part 3 – PaaS versus CaaS to Deploy Containers in Azure
14
Part 4 – Ensuring Continuous Integration and Continuous Deployment on Azure
17
Assessments

Exploring Azure App Service deployment slots

Azure App Service supports continuous deployment. The code that is pushed to source control will then be pushed out to the web app automatically. With deployment slots, we can validate changes before pushing the code to production and, of course, we can revert to the previous version if there’s a problem. The App Service plan defines the number of deployment slots that are available to you. In the Free, Shared, or Basic plans, you don’t have any deployment slots. When you move up to a Premium or Isolated plan, you have up to 20 deployment slots. Each deployment slot has its own hostname, which allows for testing. When you deploy an app to a deployment slot, it’s warmed up and this eliminates the downtime when the app is swapped into the production environment.

We can also clone instances within deployment slots. When we clone an instance or an app, the app settings, connection strings, language, framework versions...