Scaling Your Front-End in a Realistic Way!
summary
Argues that scalability is achievable with concrete practices: use component architecture (example: extract header icons into a reusable component), prefer GraphQL when REST returns a mammoth JSON, segment features with microfrontends so two teams ship parallel, and adopt caching, lazy loading and asset optimization to preserve performance as users grow. Emphasizes separation of concerns, state management, linting and automated tests to avoid costly refactors, and a design system to stop repeated styling work. Infrastructure and team structure still limit scale.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:29What is scalability
- 6:15Symptoms of unscalable front end
- 13:20Key principles for scaling
- 21:28Scaling functionality and performance
- 24:59Team and infrastructure scaling
- 26:02Conclusion and cost of scalability
related talks
25mPrinciples for Scaling Frontend Application Development
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
39mScaling Frontend Development
40mScaling Frontend Development
52mMicro frontends: prepare for the ride
24mScaling Frontend Development using Micro-frontends
34mScalable Angular Architecture
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale