Immutable Web Applications
summary
Claim: immutable web apps cut deployment risk by building each JS bundle once per semantic version, hosting assets on immutable URLs and using the index.html as the only changing file so deploys are atomic and rollbacks are simple reversions. Implementation uses environment data on window, index.html as atomic manifest, assets published to a private npm namespace (versions are immutable) and served via npm + unpkg CDN with year-long cache headers, enabling frequent releases and rollback under two minutes.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:19Safer deployments
- 3:26Move environment variables out of the bundle
- 6:11Atomic Deployments
- 7:02Rollbacks
- 8:02A lesson in anatomy
- 8:35Deployment Manifest
- 14:10Immutable assets guaranteed
- 23:02Immutable Web Apps in a nutshell
related talks
58mWeb components and micro apps, the web technologies peacekeeper
28mFunctional Web Apps: A New Paradigm For Web Development
37mA Single Page Story
39mSustainable Client Architectures with Micro Apps
45mBuilding Isomorphic Apps (Updated)
34mWeb Components & Micro Apps: Angular, React & Vue peacefully united?
36mThe Eternal Sunshine of the Zero Build Pipeline
28mWebpack for a better development workflow