Framework Freedom with Micro Frontends
summary
Freshworks replaces iframe integration with client-side composition using single-spa and a root config that registers micro frontends by name, bundle URL and activation rule, relying on lifecycle hooks bootstrap, mount, unmount to lazy load Ember and React bundles (including Ember 3.4 and 3.8 alongside React). The system works but surfaces concrete problems: unified URL asset resolution, synchronizing independent blue-green deployments, sharing a design system and React versions, and coordinating cross-app communication so framework freedom carries ongoing operational cost.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:29Business shift to unified experience
- 4:33Why micro frontends
- 9:08Building micro frontends
- 13:23How single-spa works
- 17:13Real-world implementation
- 19:20Challenges with micro frontends
- 21:45Types of micro frontends
- 23:37Conclusion and trade-offs
related talks
36mMicro Frontends in Action!
45mMicro Frontends in Action!
24mScaling Frontend Development using Micro-frontends
57mMicro Frontends – a strive for fully verticalized systems
46mScaling Micro-Frontends with Custom Elements
34mIntroduction to Micro Frontends
37mIntroduction to Micro Frontends
36mMicro Frontends - Breaking Monoliths
