Breaking the Monolithic Front-end (A HackerRank's case study)
summary
Explains HackerRank’s move from a single large frontend repo to multiple smaller repositories, detailing the problems with the monolith and the reasons for choosing a multi-repo architecture. Covers the progressive migration strategy, the chosen multi-repo structure, build/deploy pipelines, separating frontend-infra as a module, techniques for cross-repo local development and dependency management, and an open-source tool (packagebind) for improving cross-repo development.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:09Reduce the app complexity
- 3:22Separate deployment
- 5:18Bottleneck for Innovation
- 8:57Break the monolith repol
- 9:53Modules as node packages
- 11:28Keeping the code style uniform
- 12:05Publishing Modules
- 14:39Automate deployment for modules
- 18:29Managing cross dependencies
related talks
39mMicro-Frontend and Monorepo: Keys to Scaling Development
41mMicro-frontends: the golden circle
24mMicrofrontends
22mBreak Up With Your Frontend Monolith
50mOne Frontend App to Rule Them All 💍🌋
29mFrom Monolithic Web App to Micro-Frontends – Extending Microservices Architecture to the Frontend
36mMicro Frontends - Breaking Monoliths
21mEmbracing Micro-frontends: A Comprehensive Guide for Modern Web Development