Break Up With Your Frontend Monolith
summary
An 11‑year‑old Goethe Fraga site with thousands of legacy lines splits into micro frontends; claim is that an app shell plus per‑page manifests lets independently developed pieces load fast and keep shared header/footer persistent. Implementation uses a single repo, naming prefixes, and a living style guide for shared UI. Tradeoffs: increased redundancy, extra scripting and error‑handling, but faster onboarding, smaller tests, resilient partial failures, and measurable speed and maintainability gains after a few months.
AI-written summary · about
chapters (11)
- 0:00Intro
- 3:29The history
- 5:39microservices
- 5:52how microservices evolved
- 7:20different approaches to microservices
- 10:48complete opposite of code
- 12:59second date
- 14:13current state
- 16:06retrospective
- 17:52mission faced
- 18:27start small
related talks
38mBreak Up With Your Frontend Monolith
36mMicro Frontends - Breaking Monoliths
27mMicro Frontends: Break Up You Web App!
44mFrontend monoliths — an amicable separation?
57mMicro Frontends – a strive for fully verticalized systems
31mMigrating from Monolith to Microfrontends
41mMicro-frontends: the golden circle
19mHarnessing Microfrontends: Platforms for Web Apps