SPAs are dead. Long live Microfrontends.
summary
Argues SPAs act like frontend monoliths and cites a homepage shipping 9.4 MB with 5.9 MB unused, plus costly full-app deploys and painful upgrades. Describes a microfrontend stack that assembles independent bundles into HTML shells via a Node assembly layer (uses Tailor), keeps packages in a mono-repo with Lerna, and uses Webpack externals to avoid duplicating React. Demo shows rebuilding one micro app produces a new bundle and updates the page without redeploying the whole site, and suggests cloud functions for serverless deploys or Docker for SSR.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:40Single Page Apps
- 4:01Challenges
- 8:25Building Software
- 13:39Tools Libraries
- 15:46Architecture
- 17:07Demo
- 20:27Folder structure
- 28:29Cloud Functions
related talks
24mScaling Frontend Development using Micro-frontends
46mMicro Frontends, Keep Using That Word, I Don’t Think It Means What You Think It Means
29mFrom Monolithic Web App to Micro-Frontends – Extending Microservices Architecture to the Frontend
51mMicro Frontend: the microservice puzzle extended to frontend
36mMicro Frontends in Action!
55mTechnology agnostic microservices at SPA frontend
45mMicro Frontends in Action!
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends