Azure 应用服务中的横向扩展如何工作? [英] How does scaling out work in Azure App Services?

问题描述

我正试图围绕 Azure 应用服务计划和 Azure 应用服务的概念展开思考，但没有成功.

I am trying to wrap my head around the concept of Azure App Service plan and Azure App Services, with no luck.

我的理解是应用服务计划定义了容量和定价，分配给特定应用服务计划的所有应用都将共享相同的资源，对吗?

My understanding is that an App Service Plan defines the capacity and the pricing, all apps assigned to a specific App Service plan will share the same resources, is that right?

如果这是正确的，那么横向扩展有什么好处?如果横向扩展将创建相同应用的更多实例，这些实例最终将托管在相同的应用服务计划上(共享相同的资源)?

If that is right, then what is the benefit of the scaling-out? If the scale out will create more instances of the same app which at the end will be hosted on the same App Service Plan (sharing the same resources)?

我阅读了几乎所有有关 Azure 应用服务计划和应用服务的官方和非官方文档，但找不到这个问题的答案，他们都说缩放正在应用级别(而不是应用服务plan)，同时又说分配到同一个应用服务计划的应用实际上是共享相同的资源，那么横向扩展功能有什么好处呢?

I read almost all the official and non-official documentation about Azure App Service plan and App Services but couldn't find an answer to this question, they are all saying that scaling is working on the app level (not the app service plan) and at the same time saying that the apps assigned to the same app service plan are actually sharing the same resources, so what is the benefit of the scale-out feature?

问候，

推荐答案

我的理解是应用服务计划定义了容量和定价，分配给特定应用服务计划的所有应用都将共享资源，对吗?

My understanding is that an App Service Plan defines the capacity and the pricing, all apps assigned to a specific App Service plan will share the same resources, is that right?

是的.

如果这是正确的，那么横向扩展有什么好处?如果向外扩展将创建同一应用程序的更多实例，最后将托管在相同的应用服务计划上(共享相同的资源)?

If that is right, then what is the benefit of the scaling-out? If the scale out will create more instances of the same app which at the end will be hosted on the same App Service Plan (sharing the same resources)?

没有人会强迫您将所有应用都放在同一个应用服务计划中.创建应用程序时，您将其放入某个应用程序服务计划中.该(且仅此)应用服务计划中的所有应用都将共享资源，但您可以创建大量应用服务计划.
此外，当您横向扩展时，您会创建更多托管应用程序的 VM 的 PaaS 实例，因此当您横向扩展时，您不会在同一个 IIS 中获得另一个应用程序池，而是在另一个 VM 上的另一个 IIS 上获得另一个应用程序池.

No one forces you to put all your apps on the same App Service Plan. When you create an App you put it into some App Service Plan. All the Apps on that (and only that) App Service Plan would share resources, but you could create a lot of App Service Plans.
Also, when you scale out you create more PaaS instances of the VM's hosting your App, so when you scale out you are not getting another App Pool in the same IIS, you are getting another App Pool on the other IIS on the other VM.

为了澄清评论，应用服务计划是安装了 IIS 的 Windows VM 的集合.分配给该应用服务计划的所有应用都托管在这些 VM 的所有实例上，当您横向扩展或纵向扩展时，您会更改这些 VM 的数量或容量.
没有临时应用服务计划.您为服务计划付费，而不是为应用程序付费. 应用程序不花钱，它们只是在服务计划上消耗资源，它是吃"钱的服务计划.您将根据服务计划层级和规模收取费用.
定价取决于您运行的 VM 实例的大小和数量.

edit: to clarify the comment, the App Service Plan is a collection of Windows VM's with IIS installed on them. All the Apps assigned to that App Service Plan are hosted on ALL the instances of those VM's, when you scale out or scale up you change the number or capacity of those VM's.
There's no temporary App Service Plan. You pay for the Service Plan, not for the App. Apps cost nothing, they are simply consuming resources on the Service Plan, its the Service Plan that "eats" money. You are getting billed according to the Service Plan tier and scale.
Pricing is based on the size and number of VM instances you run.

这篇关于Azure 应用服务中的横向扩展如何工作?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！