Break up a Massive Vue Front End
summary
A monolithic Vue app becomes multiple repos: about 40 contributors split into independent feature or “child” apps that build, test in Docker, and publish as child apps published to npm; a thin shell stitches versions, runs targeted end‑to‑end suites, and uploads immutable JS bundles to S3 so browsers request versioned assets. CI hooks auto‑open PRs, QA gets preview URLs, semver governs breaking changes, and rollbacks simply point clients to the previous asset version. The setup speeds local builds and lets teams deploy independently.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 8:22Breaking up the monolith
- 10:45Architecture overview
- 27:42Developer workflow
- 34:49Rollbacks and emergencies
- 35:09Steps to implement
- 38:17Q&A and alternatives
related talks
56mMicro Frontends with Vue.js
23mSuperpositioned Vue componentes with Module Federation
31mBuilding Components for Vue 2&3 - an Attempt at solving the challenge
29mFrom Monolithic Web App to Micro-Frontends – Extending Microservices Architecture to the Frontend
19mHarnessing Microfrontends: Platforms for Web Apps
36mMicro Frontends - Breaking Monoliths
06mMigrating a Large Legacy App to Vue
26mMaintaining OSS like vue-cli, vue-devtools, vue-apollo and more!