Azure App Service deep dive
summary
Belief: Azure App Service works as a PaaS that makes workers stateless by externalizing state, with app service plan sizing and auto scale that adds instances in seconds and a slot swap that takes ~1–2 minutes; deployments use FTP Web Deploy local Git or CI, configuration overrides inject into environment variables, backups produce ZIPs to a storage account, logs stream live and Kudu exposes a Kudu virtual file system and webhooks, webjobs run continuous or triggered (auto‑restart on exit), containers run on Linux and a hybrid connection can surface a laptop MySQL to the app.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:06Scalable architectures for Web
- 7:49Deployment options
- 15:55Inbound Security
- 19:56Governance
- 26:46Background code
- 31:03Kudu Technology
- 35:01Linux options
- 39:38(some) Advanced scenarios
related talks
58mAdvanced Azure App Services
01h 00mApp deployment PaaS battle!
36mContinuous Deployment, Testing in Production, Autoscaling and Business Workflows
18mAzure Spring Apps: The easy way to run your apps
54mBuilding Azure Apps
31mAzure DevOps for System Engineers
27mAzure Static Web Apps for the Enterprise
44mBuilding a Global App With Azure PaaS