Are You Being Servered? — Exploring A "Serverless" Web
summary
Argument: pre-render pages to a CDN and use serverless functions only for the gaps, reducing attack surface and cache complexity. Demonstrations: a static clock that triggers builds every minute (≈455,517 runs) and a user-generated “lolly” site that uses 11ty to prebuild pages, stores records in FaunaDB, and writes/serves new entries via Netlify functions plus a webhook-triggered rebuild and fallback dynamic function when a page isn’t yet generated.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 1:27What is serverless really
- 8:03JAMstack explained
- 14:45Pre-rendering benefits
- 20:18Serverless on demand
- 26:40Live demo of vlolly.net
- 30:56Q&A and closing
related talks
44mAre you being servered? - exploring a serverless web
37mAre you being servered? — exploring a serverless web
51mJAMstack: Silly name, serious stuff
44mJAMstack: Web Apps at Ludicrous Speed
41mStatic Sites and Serverless Functions - A Dynamic Combination
14mReact on the Jamstack
35mThe Rise of JAMStack
28mFunctional Web Apps - The Revenge of Dynamic Web Apps
