SOLID Frontend Architecture. Do we need it? Yes!
summary
Argues that the frontend requires the same engineering as backend: a high‑level blueprint that separates views, models, services and modules, plus centralized state and error management, routing and performance/security checks. Demonstrates using Angular/React patterns, Redux/ngrx options, static checks (npm audit, outdated), Docker/Kitematic and SonarQube to enforce quality, shows a real repo with 261 vulnerabilities, another with 0% test coverage and one with 68% duplicated code, and recommends applying SOLID principles and cognitive‑complexity metrics.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:02The state of front-end
- 3:24Front-end vs. back-end history
- 6:17Technology and trends
- 8:37Architectural parallels
- 11:44Front-end design patterns
- 16:02Software engineering as science
- 18:30Blueprint for quality
- 23:04Implementation strategy
- 27:55Code review and analysis
- 37:10Automation and metrics
- 47:21Conclusion
related talks
46mFunctional Frontend. Practical survival guide for backend engineers.
30mThe Art of Front-end Architecture
18mSoftware Architecture Building Better Applications with Architecture Best Practices
22mHow to make robust and scalable front-end using layers
34mWe need to talk about the front web
44mFrontend Architecture for Microservices
01h 10mThe Future of Frontend Panel
40mScaling Frontend Development