Skip to content

Instantly share code, notes, and snippets.

@joelowrance

joelowrance/5- Scale an App Service web app to efficiently meet demand with App Service scale up and scale out.md

Last active March 27, 2021 15:27
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save joelowrance/6810f63fa54aa74d68c0a5df6bceeadf to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save joelowrance/6810f63fa54aa74d68c0a5df6bceeadf to your computer and use it in GitHub Desktop.
Download ZIP
5- Scale an App Service web app to efficiently meet demand with App Service scale up and scale out
Raw
5- Scale an App Service web app to efficiently meet demand with App Service scale up and scale out.md

Scale a web app manually

Example is hotel reservations - you know when busy season is.

App Service plans and scalability

Free tier is 1GB and 10 apps, shared instance, no SLA, 60 mins compute per day (dev) Shared goes up to 100 apps, 240 mins compute per day Basic has unlimited and supports scaling to 3. 99.95% SLA. 3 sublevels Standard can scale to 10. 99.95% SLA, has 3 sublevels Premium 20 instances, 99.95%, multiple sublevels of hardware Isolated 100 instances.

Not all tiers are available for all OS (no shared linux)

Monitor and scale a web app

Key to scaling is to know when to do it. Simplest way is to use the portal.

Exercise - Scale a web app manually

Used the portal to

  • select the number of instances
  • monitor errors, cpu, memory, etc

Scale up a web app

Scale out is more instances at the same hardware level.
Scale up is different hardware.
Scaling up can cause an interruption in service and IP addresses can change

Exercise - Scale up a web app

Used to portal to

  • change the app service plan to something bigger (and more expensive)
  • watched the metrics
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment