How to make robust and scalable front-end using layers
summary
Argues that splitting front-end into presentation, presenter and model layers plus clear separation of command-query separation yields more testable, maintainable code; demonstrates patterns on Angular with NgRx/Redux, using selectors and effects, dispatching actions to a central store as single source of truth to simplify caching and side‑effects. Gives concrete migration context: a 40+ person B2B team rewrites an AngularJS app for ~2 years and recently moved to Angular r12, reporting easier onboarding and predictable complexity growth.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:26Company and product
- 3:15Classic pattern problems
- 5:03Domain and interaction logic
- 7:10Why architecture matters
- 9:21Sequence and CQRS principles
- 11:49Layer separation scheme
- 13:57MVP layer details
- 16:49Constraints and challenges
- 18:38Recommendations and conclusions
- 19:00Q&A
related talks
34mScalable Angular Architecture
26mScalable Angular Architecture
27mAngular Architecture: From Patterns to Implementation
46mMicro Frontend: the microservice puzzle extended to frontend
05mMigrating a Portfolio of Front-End Apps to Angular
40mFRONTEND CHOICES
30mThe Art of Front-end Architecture
29mHow we did everything wrong and got away with it (Angular success story)