How to build front-end web apps that scale
summary
Claims a reproducible workflow: group assets by feature, run features in isolation with a workbench, and route all interfeature calls through a service registry. Demonstrations use BladeRunnerJS and MVVM testing to cut a flaky eight‑hour selenium suite to under thirty minutes. Real project numbers: ~1,000 JS files, 131k lines of code, 95k lines of tests and ~250k assets. Emphasis is on fake services for offline development, fast reloads, and bundling intelligence that swaps fakes for real services at deploy time.
AI-written summary · about
chapters (8)
related talks
01h 07mModern Frontend Engineering
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
41mMicro-frontends: the golden circle
51mBuilding Amazing Single Page Applications the Right Way
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
24mScaling Frontend Development using Micro-frontends
27mMicro Frontends: Break Up You Web App!
30mThe Recipe For Scalable Frontends