In terms of web applications, underlying infrastructure plays a vital role in coping with application performance, complex logic, traffic surges, and long-running processor execution times. it is one of the most difficult jobs to calculate the specifications in terms of infrastructure for web applications, whether it is public-facing applications or for a particular company.  It is one of the most difficult jobs to calculate the specifications in terms of infrastructure for web applications.

In many cases, there is a high chance that there will be a requirement to upgrade infrastructure specifications after a certain threshold, or maybe resources are not utilized properly. This is another difficult job for developers, DevOps engineers, or even for management to upgrade those resources. It may results in application downtime, unstable or sometimes modifications in code level,

In terms of web applications, underlying infrastructure plays a vital role in coping with application performance, complex logic, traffic surges, and long-running processor execution times. it is one of the most difficult jobs to calculate the specifications in terms of infrastructure for web applications, whether it is public-facing applications or for a particular company.  It is one of the most difficult jobs to calculate the specifications in terms of infrastructure for web applications.

In many cases, there is a high chance that there will be a requirement to upgrade infrastructure specifications after a certain threshold, or maybe resources are not utilized properly. This is another difficult job for developers, DevOps engineers, or even for management to upgrade those resources. It may results in application downtime, unstable or sometimes modifications in code level, as well as being quite expensive overall.

Scaling in Azure App Service

Scale-Up and Scale-Out are two primary workflows for Scaling.

Scale-Up (Vertical scaling)

In this scaling option, we can modify the instance power in terms of CPU, memory, disk space which directly impact the cost. This scale-up is done by changing the pricing tier of the app service plan. Additionally, based on the pricing tier, different useful features are available with the azure app service like custom domains and certificates, staging slots, autoscaling, instances, daily backups, and many more.

Scaling is quite easy to do in azure, I prefer from the portal, portal.azure.com.

Simply log in to the portal, open your app service then you will see the following options for scaling:

In the scale-up, we can see the distinct categories:

• Dev/Test
• Production
• Isolated

Dev/Test

As the name suggests, this category is used for development and testing purposes of the applications with Azure App Service.

There are five separate pricing tiers in the Dev/Test category, as shown below:

F1(free one), D1, B1, B2 and B3

We can see from the above illustration that the resources as well as tentative cost per month based on these pricing tiers.

F1 Pricing tier(Free Tier)

• No feature
• Share Infrastructure 1GB Memory/1GB Storage
• 60 minutes/day compute

D1 Pricing Tier

• Custom domain feature

• Share Infrastructure 1GB Memory
• 240 minutes/day compute

There is no SLA provided for this service plan and is metered on a per-app basis.

Basic Service Plan(B1,B2 and B3)

This plan is for low-traffic applications where we don’t need auto-scaling and traffic management features. Built-in network load balancing support automatically distributes traffic across instances.

B1 Hardware

• 100 total Azure computing units
• 1.75 GB Memory and 10 GB disk storage
• A-series computing equivalent

B2 and B3 have the same features as B1, however, hardware contents are different.

Production

As the name suggests, this category for the production workloads of the applications. Again, there are two types under this category: standard and premium pricing tiers.

This category has a standard pricing tier, S1, S2, and S3, and premium tier P1V2, P2V2, P3V2, P1V3, P2V3, and P3V3.

All these tiers have custom domains/SSL, Auto Scale, Staging Slots, Daily backups, and Traffic manager features.

Standard Service Plan

Pricing is based on the size and number of instances you run. Built-in network load balancing support automatically distributes traffic across instances.

S1, S2, and S3 are available pricing tiers in this with following specifications,

• Auto Scale up to 10 instances
• 5 Staging Slots
• 10 times daily backup
• S1: 100 ACU, 1.75 GB memory, and 50 GB storage
• S2: 200 ACU, 3.5 GB memory, and 50 GB Storage
• S2: 400 ACU, 7 GB memory, and 50 GB Storage
• All these are A-series equivalent

Premium Service Plan

This service plan is intended for enhanced performance with a faster processor, SSD storage, and double memory-to-core ratio compared to standard.

Premium V3

Faster processor, Hyper-V virtualization, and support for VNet connectivity P1, P2, P3, P1V2, P2V2, P3V2, P1V3, P2V3, and P3V3 are available pricing tiers for this option with the following specifications.

• Auto Scale up to 20 instances
• 20 Staging Slots
• 50 times daily backup
• P1: 100 ACU, 1.75 GB memory, and 250 GB storage
• P2: 200 ACU, 3.5 GB memory, and 250 GB Storage
• P2: 400 ACU, 7 GB memory, and 250 GB Storage
• P1V2: 210 ACU, 3.5 GB memory, and 250 GB storage
• P2V2: 420 ACU, 7 GB memory, and 250 GB Storage
• P3V2: 840 ACU, 14 GB memory, and 250 GB Storage
• P1V3: 195 minimum ACU/vCPU, 2vCPU, 8 GB memory, and 250 GB storage
• P2V3: 195 minimum ACU/vCPU, 4vCPU, 16 GB memory, and 250 GB storage
• P3V3: 195 minimum ACU/vCPU, 8vCPU, 32 GB memory, and 250 GB storage

The new PremiumV3 pricing tier provides us quite faster processors, SSD storage, and quadruples the memory-to-core ratio of the existing pricing tiers (double the PremiumV2 tier). With the performance benefit.

Isolated Service Plan

This service plan is specifically considered for mission-critical workloads, that are required to operate in a virtual network. An ASE is a powerful feature offering of Azure App Service that gives network isolation and improved scale capabilities. This service plan enables consumers to run their applications in private, dedicated environments in Azure datacenter using Dv2-series VMs, which is also called as App Service Environment. The plan can scale to 100 instances with more available upon request.

This service plan has been enhanced for workloads demanding resource isolation, maximum scalability, and advanced networking features. Isolated v2 allows customers to run their apps in a private, dedicated environment in an Azure datacenter with no public internet dependencies in the customer’s network.

as well as being quite expensive overall.

Scaling in Azure App Service

Scale-Up and Scale-Out are two primary workflows for Scaling.

Scale-Up (Vertical scaling)

In this scaling option, we can modify the instance power in terms of CPU, memory, disk space which directly impact the cost. This scale-up is done by changing the pricing tier of the app service plan. Additionally, based on the pricing tier, different useful features are available with the azure app service like custom domains and certificates, staging slots, autoscaling, instances, daily backups, and many more.

Scaling is quite easy to do in azure, I prefer from the portal, portal.azure.com.

Simply log in to the portal, open your app service then you will see the following options for scaling:

In the scale-up, we can see the distinct categories:

• Dev/Test
• Production
• Isolated

Dev/Test

As the name suggests, this category is used for development and testing purposes of the applications with Azure App Service.

There are five separate pricing tiers in the Dev/Test category, as shown below:

F1(free one), D1, B1, B2 and B3

We can see from the above illustration that the resources as well as tentative cost per month based on these pricing tiers.

F1 Pricing tier(Free Tier)

• No feature
• Share Infrastructure 1GB Memory/1GB Storage
• 60 minutes/day compute

D1 Pricing Tier

• Custom domain feature

• Share Infrastructure 1GB Memory
• 240 minutes/day compute

There is no SLA provided for this service plan and is metered on a per-app basis.

Basic Service Plan(B1,B2 and B3)

This plan is for low-traffic applications where we don’t need auto-scaling and traffic management features. Built-in network load balancing support automatically distributes traffic across instances.

B1 Hardware

• 100 total Azure computing units
• 1.75 GB Memory and 10 GB disk storage
• A-series computing equivalent

B2 and B3 have the same features as B1, however, hardware contents are different.

Production

As the name suggests, this category for the production workloads of the applications. Again, there are two types under this category: standard and premium pricing tiers.

This category has a standard pricing tier, S1, S2, and S3, and premium tier P1V2, P2V2, P3V2, P1V3, P2V3, and P3V3.

All these tiers have custom domains/SSL, Auto Scale, Staging Slots, Daily backups, and Traffic manager features.

Standard Service Plan

Pricing is based on the size and number of instances you run. Built-in network load balancing support automatically distributes traffic across instances.

S1, S2, and S3 are available pricing tiers in this with following specifications,

• Auto Scale up to 10 instances
• 5 Staging Slots
• 10 times daily backup
• S1: 100 ACU, 1.75 GB memory, and 50 GB storage
• S2: 200 ACU, 3.5 GB memory, and 50 GB Storage
• S2: 400 ACU, 7 GB memory, and 50 GB Storage
• All these are A-series equivalent

Premium Service Plan

This service plan is intended for enhanced performance with a faster processor, SSD storage, and double memory-to-core ratio compared to standard.

Premium V3

Faster processor, Hyper-V virtualization, and support for VNet connectivity P1, P2, P3, P1V2, P2V2, P3V2, P1V3, P2V3, and P3V3 are available pricing tiers for this option with the following specifications.

• Auto Scale up to 20 instances
• 20 Staging Slots
• 50 times daily backup
• P1: 100 ACU, 1.75 GB memory, and 250 GB storage
• P2: 200 ACU, 3.5 GB memory, and 250 GB Storage
• P2: 400 ACU, 7 GB memory, and 250 GB Storage
• P1V2: 210 ACU, 3.5 GB memory, and 250 GB storage
• P2V2: 420 ACU, 7 GB memory, and 250 GB Storage
• P3V2: 840 ACU, 14 GB memory, and 250 GB Storage
• P1V3: 195 minimum ACU/vCPU, 2vCPU, 8 GB memory, and 250 GB storage
• P2V3: 195 minimum ACU/vCPU, 4vCPU, 16 GB memory, and 250 GB storage
• P3V3: 195 minimum ACU/vCPU, 8vCPU, 32 GB memory, and 250 GB storage

The new PremiumV3 pricing tier provides us quite faster processors, SSD storage, and quadruples the memory-to-core ratio of the existing pricing tiers (double the PremiumV2 tier). With the performance benefit.

Isolated Service Plan

This service plan is specifically considered for mission-critical workloads, that are required to operate in a virtual network. An ASE is a powerful feature offering of Azure App Service that gives network isolation and improved scale capabilities. This service plan enables consumers to run their applications in private, dedicated environments in Azure datacenter using Dv2-series VMs, which is also called as App Service Environment. The plan can scale to 100 instances with more available upon request.

This service plan has been enhanced for workloads demanding resource isolation, maximum scalability, and advanced networking features. Isolated v2 allows customers to run their apps in a private, dedicated environment in an Azure datacenter with no public internet dependencies in the customer’s network.