扩展在Azure App Services中如何工作? [英] How does scaling out work in Azure App Services?

问题描述

我想尽一切努力来解决Azure App Service计划和Azure App Services的概念.

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 App Service计划和App Services的官方和非官方文档，但找不到该问题的答案，他们都说扩展在App级别上起作用(而不是App Service)计划)，同时说分配给同一应用程序服务计划的应用程序实际上共享相同的资源，那么横向扩展功能的好处是什么?

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)?

没有人会强迫您将所有应用程序置于同一应用程序服务计划中.创建应用程序时，您会将其放入某些应用程序服务计划中.该(且仅此)应用服务计划上的所有应用都会共享资源，但是您可以创建很多应用服务计划.
另外，横向扩展时，将创建更多虚拟机托管您的应用程序的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.

为澄清评论，App Service计划是Windows VM的集合，其中已安装IIS.分配给该应用程序服务计划的所有应用程序都托管在这些VM的所有实例上，当您扩展或扩展时，可以更改这些VM的数量或容量.
没有临时的应用服务计划. 您为服务计划付费，而不是为应用程序付费. 应用程序不花钱，它们只是在消耗服务计划中的资源，该服务计划浪费"了金钱. 您将根据服务计划层级和规模向您收取费用 .
Pricing is based on the size and number of VM instances you run.

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 App Services中如何工作?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！