RedditPP Mascot

RedditPP

r/AZURE • … • u/InitializedVariable

App Services Plan architecture?

Hey folks, I’m curious about your thoughts when it comes to App Service Plans — specifically when it comes to consolidating Services.

In previous environments I’ve been in, multiple client-specific instances of a certain Service were hosted on the same Plan. This worked fine so long as the Plan was sized appropriately for the resource demands of the associated Services.

In my current environment, basically every Service has a dedicated Plan. I’m thinking there might be opportunities to improve manageability and cost efficiency by consolidating.

For the sake of discussion, let’s say you are looking to host an online store made up of the following components, with all Services based on a common OS:

- Customer-facing website - An inventory management portal - Supporting APIs

The customer-facing website would need to scale out based on utilization, so it would make sense to size the Plan to allow for this.

The inventory management portal would likely have less resource demands, and thus could be hosted on a smaller Plan.

Would you create 1 or more dedicated Plans for the APIs, or host them alongside the associated Services?

Would you actually host everything on a single, big Plan?

Have you found that the cost of having multiple small Plans isn’t considerably higher than a few large ones?

Or, that consolidating to fewer Plans has implications such as resource contention?

Any other considerations?

**EDIT:** Based on the comments so far, I’m starting to think the best way to approach this is to look at Plans simply as *scale sets* for a Service. Thanks for helping me think through this.

**EDIT 2:** It turns out that per-site scaling is in fact supported, even if it is not configurable in the portal: https://learn.microsoft.com/en-us/azure/app-service/manage-scale-per-app

— 0