Book Image

Hands-On Cloud Solutions with Azure

By : Greg Leonardo
Book Image

Hands-On Cloud Solutions with Azure

By: Greg Leonardo

Overview of this book

Azure provides cloud-based solutions to support your business demands. Building and running solutions on Azure will help your business maximize the return on investment and minimize the total cost of ownership. Hands-On Cloud Solutions with Azure focuses on addressing the architectural decisions that usually arise when you design or migrate a solution to Microsoft Azure. You will start by designing the building blocks of infrastructure solution on Azure, such as Azure compute, storage, and networking, followed by exploring the database options it offers. You will get to grips with designing scalable web and mobile solutions and understand where to host your Active Directory and Identity Solution. Moving on, you’ll learn how to extend DevOps to Azure. You will also beneft from some exciting services that enable extremely smooth operations and streamlined DevOps between on-premises and cloud. The book will help you to design a secure environment for your solution, on both the Cloud and hybrid. Toward the end, you’ll see how to manage and monitor cloud and hybrid solutions. By the end of this book, you will be armed with all the tools and knowledge you need to properly plan and design your solutions on Azure, whether it’s for a brand new project or migration project.
Table of Contents (16 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

What are deployment slots?


Deployment slots are parallel containers that exist within an Azure resource, such as App Services. These slots can be used as environments, such as staging, QA, or dev. I leverage slots as a staging environment that can be used to test code being deployed in a production environment. Once you are done with your verification testing, you can switch slots for zero downtime. Now, as I mentioned, you can use them for QA and dev environments but this can create issues with downstream resources such as databases or services. I always prefer and recommend keeping a division between environments, for data security, access, and so on, as you can see in the following daigram:

Deployment slots

Deployment slots:

  • They act like an App Service instance
  • The main slot is referred to as the production slot
  • They can leverage the configuration of App Services
  • They are scaled by App Service Plan and are not separate
  • The pricing is included with the App Service Plan
  • They have their own URL...