[Azure Computing] Azure App Service 와 Azure App service Plan

 

 

오늘부터 시작해서 이번주 15일 204 시험을 위해 포스팅을 시작해보려고 한다.

처음 주제는 App Service 에 관련된 호스팅이다.

204 시험은 개발자를 위한 코스이기 때문에 실제 코드를 쉽게 짜고 배포하는 방법에 대한 소개가 많이 나와있다.

그중 Azure App Service 는 다양한 언어의 코드를 빠르게 배포하고 호스팅 해주는 툴이다. 공식 문서에 나와있는 정의를 살펴보면 아래와 같다.

---

Azure App Service

Azure App Service is an HTTP-based service for hosting web applications, REST APIs, and mobile back ends. You can develop in your favorite language, be it .NET, .NET Core, Java, Ruby, Node.js, PHP, or Python. Applications run and scale with ease on both Windows and Linux-based environments.

App Service not only adds the power of Microsoft Azure to your application, such as security, load balancing, autoscaling, and automated management. You can also take advantage of its DevOps capabilities, such as continuous deployment from Azure DevOps, GitHub, Docker Hub, and other sources, package management, staging environments, custom domain, and TLS/SSL certificates.

With App Service, you pay for the Azure compute resources you use. The compute resources you use are determined by the App Service plan that you run your apps on.

---

App Service plan

When you create an App Service plan in a certain region (for example, West Europe), a set of compute resources is created for that plan in that region. Whatever apps you put into this App Service plan run on these compute resources as defined by your App Service plan. Each App Service plan defines:

1) Region (West US, East US, etc.)

2) Number of VM instances

3) Size of VM instances (Small, Medium, Large)

• Small (2 CPU core, 8 GiB of memory)
• Medium (4 CPU cores, 16 GiB of memory)
• Large (8 CPU cores, 32 GiB of memory) 

4) Pricing tier (Free, Shared, Basic, Standard, Premium, PremiumV2, PremiumV3, Isolated)

• Shared compute: Free and Shared, the two base tiers, runs an app on the same Azure VM as other App Service apps, including apps of other customers. These tiers allocate CPU quotas to each app that runs on the shared resources, and the resources cannot scale out.
• Dedicated compute: The Basic, Standard, Premium, PremiumV2, and PremiumV3 tiers run apps on dedicated Azure VMs. Only apps in the same App Service plan share the same compute resources. The higher the tier, the more VM instances are available to you for scale-out.
• Isolated: This tier runs dedicated Azure VMs on dedicated Azure Virtual Networks. It provides network isolation on top of compute isolation to your apps. It provides the maximum scale-out capabilities.
• Consumption : This tier is only available to function apps. It scales the functions dynamically depending on workload.

---

Limitations

• App Service on Linux is not supported on Shared pricing tier.
• You can't mix Windows and Linux apps in the same App Service plan.
• Historically, you can't mix Windows and Linux apps in the same resource group. However, all resource groups created on or after January 21, 2021 do support this scenario. For resource groups created before January 21, 2021, the ability to add mixed platform deployments will be rolled out across Azure regions (including National cloud regions) soon.
• The Azure portal shows only features that currently work for Linux apps. As features are enabled, they're activated on the portal.
• When deployed to built-in images, your code and content are allocated a storage volume for web content, backed by Azure Storage. The disk latency of this volume is higher and more variable than the latency of the container filesystem. Apps that require heavy read-only access to content files may benefit from the custom container option, which places files in the container filesystem instead of on the content volume.

 

---

Reference

출처1 : docs.microsoft.com/en-us/learn/paths/deploy-a-website-with-azure-app-service/

출처2 : docs.microsoft.com/en-us/azure/app-service/

출처3 : docs.microsoft.com/en-us/azure/app-service/overview-hosting-plans