Book Image

Implementing Azure: Putting Modern DevOps to Use

By : Florian Klaffenbach, Oliver Michalski, Markus Klein, Mohamed Waly, Namit Tanasseri, Rahul Rai
Book Image

Implementing Azure: Putting Modern DevOps to Use

By: Florian Klaffenbach, Oliver Michalski, Markus Klein, Mohamed Waly, Namit Tanasseri, Rahul Rai

Overview of this book

This Learning Path helps you understand microservices architecture and leverage various services of Microsoft Azure Service Fabric to build, deploy, and maintain highly scalable enterprise-grade applications. You will learn to select an appropriate Azure backend structure for your solutions and work with its toolkit and managed apps to share your solutions with its service catalog. As you progress through the Learning Path, you will study Azure Cloud Services, Azure-managed Kubernetes, and Azure Container Services deployment techniques. To apply all that you’ve understood, you will build an end-to-end Azure system in scalable, decoupled tiers for an industrial bakery with three business domains. Toward the end of this Learning Path, you will build another scalable architecture using Azure Service Bus topics to send orders between decoupled business domains with scalable worker roles processing these orders. By the end of this Learning Path, you will be comfortable in using development, deployment, and maintenance processes to build robust cloud solutions on Azure. This Learning Path includes content from the following Packt products: • Learn Microsoft Azure by Mohamed Wali • Implementing Azure Solutions - Second Edition by Florian Klaffenbach, Oliver Michalski, Markus Klein • Microservices with Azure by Namit Tanasseri and Rahul Rai
Table of Contents (29 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

App Service plans


When you create an App Service, such as a Web App for example, you will be asked to specify the App Service plan.

An App Service plan is like the hardware host on which you run your VMs. It contains the resources that are shared among the App Service. As a result, we can look at App Service as VMs running on the host, which is the App Service plan.

The App Service plan also defines many settings for the App Service that will be built on it, such as the region, number of instances, whether it will be able to scale out/in or not, and much more, which will be covered later on.

Azure offers different plans to fulfill different customers' needs, such as the following:

  • Shared infrastructure plans:
    • Free plan: This is the entry level plan, and as its name implies, it's available for free. It's meant for dev/test scenarios, or if you wish to deploy a website for temporary purposes, where your app would be running with other apps on the same VM with a limited CPU quota per day and no...