The Rise of JAMStack
summary
Argues that the web shifts from server-rendered LAMP/MEAN assumptions to a CDN‑served architecture where JavaScript, APIs and markup are prebuilt: JAMstack driven by React, Gatsby/Sapper/Jekyll/Hugo, AWS Lambda and specialist APIs. Shows measured constraints (performance budget ≈170 KB, median page ≈400 KB), cites PayPal.me and a sports‑betting site as working JAMstack builds, and demonstrates Netlify features like deploy previews and server‑side analytics; runtime functions and static hosting actually reduce surface area and cost.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:25DISTRIBUTION
- 10:50JAVASCRIPT GOT SERIOUS
- 11:49FULL STACK JAVASCRIPT
- 12:32CLIENTSIDE RENDERING & ROUTING
- 13:36Web Performance Budgets
- 14:42SINGLE PAGE APPS
- 15:18CLIENT-SIDE RENDERING
- 17:48GIT BASED, CI/CD WORKFLOW
- 18:44THE API ECONOMY
- 20:54SERVERLESS
- 21:45BUILD TOOLS
- 22:25STATIC SITE GENERATORS
- 29:21THESE ARE JAMSTACK
- 31:39DEVELOPER EXPERIENCE
- 33:52THE OPEN WEB








