Frontend Monoliths: Run if you can!
summary
Argues that single‑page apps create frontend monoliths that block independent teams and proposes the open‑source Scion Workbench Application Platform (Angular-based) that gives each micro‑frontend a sandbox (iframe/shadow DOM), integrates by URL, and routes interactions via an application manifest and intent/capability matching. Demo shows a contact Angular app and a React “joke” app integrated into one host, using the guest API for actions and runtime isolation. Designed for scenarios with ~40 parallel teams; demo mostly works after a manifest typo fix.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 0:45Web page size
- 4:08Speed is money
- 5:43The history of enterprise application
- 6:40The future of the web
- 7:55Frontend vs backend
- 8:54Goals of microservices
- 10:21Technology agnostic season
- 10:56Break the monolith
- 11:57Frameworks
- 12:50Libraries
- 13:23Core Problems
- 13:33Modularization
- 14:26Micro Frontend
- 14:56Demo
- 15:38Drawbacks
- 16:33Web Components
- 19:30Parallel development
- 21:03Design Workbench
- 21:47Application Journey
- 23:28URL
- 24:25Protections
- 25:25Application Platform
- 29:52Application Context
- 30:51Coding
- 32:05Contact
- 36:30Guest API
- 37:41In List
- 38:52View
- 39:51Screen
- 40:49Popup
- 45:52Integrate
- 46:56Contact Form
- 48:33Dev Tools
related talks
36mMicro Frontends in Action!
36mMicro Frontends - Breaking Monoliths
19mHarnessing Microfrontends: Platforms for Web Apps
22mBreak Up With Your Frontend Monolith
47mMicro Frontends Unmasked
44mFrontend monoliths — an amicable separation?
40mAngular, React, Vue and Co. – peacefully united thanks to Web Components and Micro Apps
36mMicrofrontends: Scalability Savior or Unmanageable Maze?