Applying Microservices Design Patterns to Scale React App Development
summary
Shows a concrete architecture: split app into independent NPM packages as microservices and a tiny core that mounts them and owns globals. Uses RxJS observables for state sharing with explicit update functions, keeps global state minimal, and manages packages in a monorepo with Lerna or Yarn workspaces. Explains code ownership via GitHub CODEOWNERS and says the approach scales to many teams and has worked well in production.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:05What issues we identified
- 7:36Local state with observables
- 10:16What we need to take care of
related talks
29mFrom Monolithic Web App to Micro-Frontends – Extending Microservices Architecture to the Frontend
49mScalable Best Practices for Your Development Team
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
46mMicro Frontends, Keep Using That Word, I Don’t Think It Means What You Think It Means
45mA Software Architect's Approach towards SPA Based Micro Apps
25mScaling React.js Applications
31mDelivering JS applications at scale
41mYou Keep Using That Word, I Don’t Think It Means What You Think