I’ve built a SPA, now what?
summary
Built a Twitter trading demo that nets $61 and uses real examples to justify architecture decisions, not buzzwords. The SPA is treated as static and served from Azure Storage (or S3) for speed and cheap bandwidth, APIs run as Azure Functions/Lambda, long-running workflows use logic apps/durable functions, sentiment analysis hooks the feed, and benchmarks show static hosting outperforms app-service style Node servers.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:00Planning Money
- 2:47Why Botas
- 8:42What is a MultiPage Application
- 9:23What is a SinglePage Application
- 9:46What does an SPI look like on disk
- 11:51Static vs dynamic requests
- 14:11Static vs dynamic
- 15:11Caching
- 18:16Serving
- 21:51Serverless
- 25:51Functions as a Service
- 30:01Orchestration to Service
- 35:51Summary
- 36:51Questions
- 38:16Performance tradeoffs
- 38:51Downsides for users
- 40:51Serverside rendering
- 42:51Detect sentiment
related talks
32mHow to scale an SPA to 1M views for $1?
59mBeing cheap with the cloud
59mServerless frontend, serverless backend, serverless security!
36mCloud First Web Apps in Azure
46mBuild serverless, full stack applications in Azure with Azure SQL
01h 01mEvent driven applications in Azure
19mHow Static Web Apps saved time and money!
47mMaking Static Dynamic - Adding SignalR to Azure Static Web Apps