How to scale an SPA?
summary
A concrete recipe: treat the SPA as static assets and host the build folder on Azure Storage or S3 to get far lower latency and cost than an App Service, use cache-control public headers and short HTML TTLs (five minutes) so CDNs and proxy caches absorb traffic, put API endpoints on serverless functions (AWS Lambda / Azure Functions) paying only per execution, and orchestrate long‑running or stateful work with Durable Functions because plain functions die after five minutes.
AI-written summary · about
chapters (11)
- 0:00Start
- 9:15What is an SPA?
- 11:14Static vs Dynamic
- 12:05Quiz
- 13:56Is an SPA dynamic or static?
- 14:39Caching
- 17:38Serving
- 20:39Server-less
- 26:47Orchestration
- 27:45Durable Functions
- 29:22Summary
related talks
58mAdvanced Azure App Services
49mDeploying Apps to the Cloud At Scale
31mFrom Code to Scale! Build a Static Web App in Minutes
45mDeploying your Static Web App with Your Favorite Framework in Minutes
52mAzure App Service deep dive
18mDeploying Secure Angular Apps that Scale
31mContainerized Deployments for your SPA and API
01h 00mBuilding Resilient Applications In Microsoft Azure