Scaling and Resilience
This course will show you how to design and create web applications using the Azure App Service.
By the end of this course, you'll have gained a firm understanding of the key components that comprise the Azure App Service. Ideally, you will achieve the following learning objectives:
- A solid understanding of the foundations of Azure web app development and deployment.
- The use cases of Azure Web Jobs and how to implement them.
- How to design and scale your applications and achieve consistent resiliency.
This course is intended for individuals who wish to pursue the Azure 70-532 certification.
You should have work experience with Azure and general cloud computing knowledge.
This Course Includes
- 1 hour and 35 minutes of high-definition video.
- Expert-led instruction and exploration of important concepts surrounding Azure Web Apps.
What You Will Learn
- How to deploy and configure Azure web apps.
- How to implement Azure Web Jobs.
- Scaling and resilience with Azure web apps.
Hello and welcome to the section on web app scaling and resilience. Scaling and resilience matters as a key feature of cloud services, cloud services such as Azure offer flexible infrastructure, available immediately, differentiating themselves from self-posted solutions, which require significant resources to maintain and grow.
Quick and easy scaling and resilience in response to changing requirements is a key offering. The infrastructure concerns of provisioning servers, networks, power, and other resources is handled by the cloud provider, allowing the customers to focus on their applications and services. Various features such as end points and virtual machine monitoring, logs and built in diagnostics help to enable resilience, and free the user from having to build this functionality themselves.
As a practical example, a company that just released their latest web app find that the demand and associated resource requirements have spiked suddenly as a side effect to the rapid success and popularity of the new app. In a self-hosted scenario, it would have to focus on provisioning the new servers and deploying the app to those servers quickly. It takes time for them to respond, purchase new hardware, have their IT department figure out how to install it, their network team prepare the low balance infrastructure, and the development teams to deploy the applications to the new servers. Later, having invested the time and money into this new infrastructure, they find that the demand for their app is diminished, and they only require a fraction of the resources to keep the application operational. However, most of their new infrastructure efforts are now an unrecoverable, sunk, cast.
Alternatively, having deployed their web app to Azure, they were able to respond to the spike in traffic within minutes or seconds, without giving a second thought to the underlying infrastructure. Later, when the demand fell, they were able to scale down to a cheaper service plan, and fewer instances, instantly minimizing their hosting cast, without the wasted infrastructure assets.
Now that we've gone over the brief overview of what web app scaling and resilience is, in the next section, we're going to discover how we can actually configure our app, and make it scalable and resilient.
About the Author
Isaac has been using Microsoft Azure for several years now, working across the various aspects of the service for a variety of customers and systems. He’s a Microsoft MVP and a Microsoft Azure Insider, as well as a proponent of functional programming, in particular F#. As a software developer by trade, he’s a big fan of platform services that allow developers to focus on delivering business value.