JAMstack: Silly name, serious stuff
summary
Claims that pre-rendering to a CDN cuts complexity and risk: Netlify-style immutable atomic deploys, GIT-triggered CI builds, and serverless functions (webtask.io) replace origin servers. Examples: a clock site that deploys every minute (341,661 runs recorded), a Google I/O Minesweeper with 25 KB payload and <5 s TTI on slow 3G, Smashing Magazine cuts load from 800 ms to 80 ms, Citrix reports ~65% annual hosting cost savings. A comments engine built this way works and reverts instantly.
AI-written summary · about
chapters (27)
- 0:00Intro
- 2:00WHAT DOES THAT EVEN MEAN
- 4:38STATIC - DYNAMIC
- 7:20STATIC VIRTUE
- 7:33LET'S TALK STACKS
- 10:42this can SIMPLIFY DEPLOYMENTS
- 10:55PROJECT COMPLEXITY
- 13:52LAUNCH DAY
- 18:16IMPACTS AND OPPORTUNITIES
- 18:27A GREATLY REDUCED SURFACE AREA
- 21:28DEPLOYMENT CONFIDENCE
- 28:44AUTOMATION REPEATABILITY / PREDICTABILITY / ACCOUNTABILITY / AGILITY
- 29:15GIT-BASED DEPLOYMENTS
- 30:37DATA SOURCES
- 35:15EXAMPLES AND RESULTS
- 35:57TURNAROUND TIME FOR UPDATES WENT FROM WEEKS TO MINUTES
- 37:17WE HAD SOME CACHING ISSUES... WITH PROBABLY EVERY SINGLE WORDPRESS CACHING PLUGIN OUT THERE
- 40:09SHIP LESS JAVASCRIPT
- 40:51AUGMENTING JAMSTACK SITES
- 41:08SERVERLESS TO THE RESCUE
- 41:40FUNCTIONS AS A SERVICE ENABLE A MICROSERVICES ARCHITECTURE
- 43:12BOUGHT SERVICES
- 43:54BUT WHAT OF THE RISK?
- 44:12DREAM CRUSHER
- 45:20TECHNICAL AND SERVICE LEVEL CONTRACTS
- 45:44SMALLER SURFACES ARE EASIER TO REASON ABOUT, AND CREATE GREATER AGILITY
- 49:43WHAT IS THE JAMSTACK?
related talks
50mDo we really need this JAMstack thing? And what even is it?
44mJAMstack: Web Apps at Ludicrous Speed
35mThe Rise of JAMStack
37mAre you being servered? — exploring a serverless web
31mJAMStack - The Total Victory of JavaScript
05mLightning talk: Give a try to the JAM(stack)
56mJAMstack
29mJamstack at Scale