Introduction to Azure App Service Environment Boston Code

Introduction to Azure App Service Environment Boston Code Camp, March 2017 Jason Haley jason@jasonhaley. com

Azure App Service Family Web Apps Web apps that scale with your business Logic Apps Automate business processes across Saa. S and on-premises Mobile Apps Build mobile apps for any device API Apps Build and consume APIs in the cloud

Demo Lap around the public app service

App Service Environment (ASE) • Premium tier service plan option • Highly scalable • For scenarios that need high RPS like the CBC News • Benchmarked 25 K RPS (HTTP) and 20 K RPS (HTTPS) • Isolated and secure • Control inbound and outbound traffic • Miniaturized version of Azure App Service • Will only contain your apps • Scale up to 50 compute resources across 3 worker pools • P 1 – P 4 scaling options

Differences • Dedicated compute resources • Not sharing infrastructure with other peoples web apps • Minimum of four machines • Created in a virtual network • Needs its own subnet • Network security groups (NSG) to lock down VNET • Can access other resources on its VNET • Can be Internal or External • Allows you to protect upstream using WAF

What makes an ASE? • Virtual Machines • Azure SQL Database • Azure Storage • VNet subnet • DNS

Network Architecture From https: //docs. microsoft. com/en-us/azure/app-service-web/app-service-environment-network-architecture-overview

A look back at Tech. Ed 2012 Windows Azure Web Sites: Under the Hood Yochay Kiriaty, Craig Kitterman

Machine Roles • Front Ends • Http/Https endpoints for apps in ASE • Load balance passing traffic to workers • Minimum of P 2 size and 2 instances • Worker Pools • Hosts/runs your apps • Limit of 3 worker pools (with up to 50 workers) • Minimum of 2 instances (can be P 1 – P 4)

Somethings can’t change • Location • Subscription • Resource Group • VNet used • Subnet size (the ASE is in)

Demo Take a look at external and internal App Service Environments

Scaling of ASEs • Front Ends • Monitor memory and CPU • Depends on traffic load (not so much work load of apps) • Can auto and schedule scaling • Worker Roles • • • Scaling out is slow (can take 3 hours) Depends on Update Domains – 2 only workers = 1 usable Need to have extra workers available to scale Depends on load of the app service plans Can auto and schedule scaling

Resources • Episode 213: Azure App Service Best Practices for Large Scale Applications (CBC News voter app) • https: //channel 9. msdn. com/Shows/Cloud+Cover/Episode-213 -Azure-App. Service-Best-Practices-for-Large-Scale-Applications • Deploying highly scalable and secure web and mobile apps • https: //azure. microsoft. com/en-us/resources/videos/azurecon-2015 -deploying -highly-scalable-and-secure-web-and-mobile-apps/ • Deep Dive into Azure App Service: A Platform to Build Modern Applications (starts ~23: 58) • https: //mva. microsoft. com/en-US/training-courses/deep-dive-into-azure-appservice-a-platform-to-build-modern-applications 16828? l=YNra. RQR 4 C_604668937