A Skeptic’s Intro To The Jamstack
summary
Argues that shipping prebuilt HTML/JS from a CDN plus selective serverless APIs (e.g. AWS Lambda serverless functions) reduces running‑server complexity and improves reliability, security, performance and cost; static site generators like Gatsby and Vuepress pre-render pages and hydrate a JS bundle so sites load faster; cites deploy previews, atomic deploys and instant rollbacks as built features, mentions PayPal.me as a real example, and traces a five‑year surge in JS frameworks and third‑party APIs.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:47DYNAMIC
- 6:20CLIENTSIDE RENDERING & ROUTING
- 7:26SINGLE PAGE APPS
- 7:55CLIENT-SIDE RENDERING
- 9:34GIT BASED, CI/CD WORKFLOW
- 10:19THE API ECONOMY
- 12:05BUILD TOOLS
- 12:42STATIC SITE GENERATORS
- 15:13THESE ARE JAMSTACK
- 16:43DEVELOPER EXPERIENCE
- 17:57THE OPEN WEB
related talks
35mThe Rise of JAMStack
31mJAMStack - The Total Victory of JavaScript
40mJAMstack: Silly Name. Serious Stuff
44mNo, Seriously… What is Jamstack?
30mRise of the Jamstack — Mathias Biilmann
26mSpreading the JAMstack
31mThe post-Jamstack world and the rise of Hybrid Frameworks
50mDo we really need this JAMstack thing? And what even is it?