JAMstack: Web Apps at Ludicrous Speed
summary
Claim: rendering as many pages as possible at build time and serving them from a CDN cuts latency and attack surface dramatically. Examples: static site generators (Gatsby, Next.js, Hugo, Eleventy, Jekyll), API services (Algolia, Stripe, Okta, Twilio, Fauna), and serverless functions for on‑demand compute. Measured wins include higher requests per second, atomic deployments and easy rollbacks, branch preview workflows, and fewer DB trips. Key tooling detail: prebuilt markup and assets, CDN edge delivery, progressive enhancement via JS and APIs.
AI-written summary · about
chapters (27)
- 0:00Intro
- 1:30My Web Application Journey
- 4:55Web Request Walk of Shame
- 16:33Cache
- 17:33Static File
- 19:37Static vs Dynamic
- 20:47Native Mobile Apps
- 22:45Ludicrous Speed
- 23:20No Code Faster
- 24:22All is Not Lost
- 24:39JAMstack Application Architecture
- 26:31Atomic Deployments
- 27:20Static Sites
- 28:09APIs
- 29:41The Experts
- 30:20Functions as a Service
- 30:44JAMstack Approach
- 31:41Time and Effort
- 32:44Managing Infrastructure
- 33:03My Past Projects
- 33:41Modern Technology
- 34:32What would I do differently
- 36:02Stressful moments
- 36:15Content management systems
- 38:22Getting started
- 39:28You cant get rid of serverside code
- 40:29Wrap up
