Micro-Frontends in the trenches Micro-Frontends & Angular with Manfred Steyer
Apr 1, 2026
Manfred Steyer, Angular trainer, consultant and creator of Native Federation, shares his experience with micro-frontends. He compares hyperlink, hydration and federation approaches. He covers state sharing with signals and subjects, handling multiple Angular versions, and why he built a bundler-agnostic Native Federation using import maps and ES modules.
AI Snips
Chapters
Books
Transcript
Episode notes
Microfrontends Fit Large Vertically Split Apps
- Micro-frontends suit large, vertically split applications rather than small projects where they add overhead.
- Manfred notes they're used regularly in big companies but become overkill if you only have one or two themes to verticalize.
Prefer Hyperlinks Then Federation When Needed
- Consider hyperlinks plus hydration as the simplest micro-frontend approach; use Module Federation only when you need seamless in-page integration.
- Manfred recommends hyperlinks for separate deployability and hydration to regain SPA benefits, using federation when users mustn't notice app boundaries.
Share Minimal Context Via Signals Or Subjects
- Avoid sharing full app state across micro-frontends; share minimal context via a service exposing signals or subjects.
- Manfred suggests services with signals/subjects for unobtrusive publish/subscribe between separately deployed units.
