1. Introduction to Azure App Service Environment
Boston Code Camp, March 2017
Jason Haley

2. Azure App Service Family
Web Apps
Web apps that scale with your business
Mobile Apps
Build mobile apps for any device
Azure App Service is a PaaS offering that comprises four separate (but related) services:
Web Apps is a fully managed compute platform optimized to host Web sites and Web applications
Mobile Apps provides infrastructure for hosting back-ends for mobile apps -- for example, it provides infrastructure for sending push notifications not only to Windows clients, but to iOS and Android clients as well
API Apps makes it easy to host APIs in the cloud, features integrated support for Swagger ( and offers a built-in authentication service for restricting access to APIs
Logic Apps allows you to automate business processes and workflow -- for example, automatically finding negative tweets about your company and sending notifications to a Slack channel
Together, these services comprise a ready-made solution to many of the challenges involved in publishing Web sites, Web apps, Web services, mobile apps, and more.
Logic Apps
Automate business processes across SaaS and on-premises
API Apps
Build and consume APIs in the cloud

3. Demo
Lap around the public app service

4. App Service Environment (ASE)
Premium tier service plan option
Highly scalable
For scenarios that need high RPS like the CBC News
Benchmarked 25K RPS (HTTP) and 20K 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
P1 – P4 scaling options

5. Differences Dedicated compute resources Created in a virtual network
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

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

7. Network Architecture
From

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

9. Machine Roles Front Ends Worker Pools
Http/Https endpoints for apps in ASE
Load balance passing traffic to workers
Minimum of P2 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 P1 – P4)

10. Somethings can’t change
Location
Subscription
Resource Group
VNet used
Subnet used
Subnet size (the ASE is in)
/25 is a good size

11. Demo
Take a look at external and internal App Service Environments

12. Scaling of ASEs Front Ends Worker Roles 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

13. Resources
Episode 213: Azure App Service Best Practices for Large Scale Applications (CBC News voter app)
Service-Best-Practices-for-Large-Scale-Applications
Deploying highly scalable and secure web and mobile apps
deploying-highly-scalable-and-secure-web-and-mobile-apps/
Deep Dive into Azure App Service: A Platform to Build Modern Applications (starts ~23:58)
service-a-platform-to-build-modern-applications ?l=YNraRQR4C_
Cidir at least /25