JAMstack
summary
JAMstack is presented as an architecture delivering sites whose speed is limited only by the network, addressing SSR and SPA problems. The presenter rebuilt a corporate blog of 10,000 items with Gatsby (noting long builds in some frameworks) and compared build times to Hugo (~5s for 10k items); the architecture serves a static bundle from hosts like GitHub/Netlify and handles dynamic features via lambda functions and third‑party services such as Shopify and Algolia for auth and search, with the main limitation being long builds when content is frequently updated.
AI-written summary · about
chapters (8)
- 0:00JAMstack in Ukraine
- 7:43Server vs client rendering
- 10:53What is JAMstack
- 22:01How JAMstack works
- 34:00Client benefits: speed and cost
- 41:12Migrating to JAMstack
- 44:48Q&A
- 55:00Summary
related talks
35mThe Rise of JAMStack
44mJAMstack: Web Apps at Ludicrous Speed
29mJamstack at Scale
24mEvolution of JamStack: Not just Static Anymore
30mRise of the Jamstack — Mathias Biilmann
30mJAMstack is the future. I think. Maybe.
42mTo Truly Understand Jamstack, Forget the JAM
51mJAMstack: Silly name, serious stuff