RTS Questionnaire · Question 29 of 52 · file: answers/q29.html
Have you worked with Micro-frontends? If yes, which architecture or framework did you use?
Micro-frontendsArchitectureFrontend
✅ Yes — I have worked with micro-frontend architectures and know how to choose between the available implementation strategies.
🧪 Interactive proof: this answer has its own page with a live micro-frontend workflow, the Module Federation config, the shell bootstrap and the runtime manifest behind it — open the Q29 micro-frontend proof →
Technical detail
- 🧩 Module Federation (webpack/Vite) — a host/shell application loading independently deployed remotes at runtime, with shared singleton dependencies (Angular/React, RxJS, design system), version negotiation and explicit exposed modules.
- 🕸️ Web Components / Angular Elements — packaging framework-agnostic custom elements that a legacy page or another framework can mount safely, useful for incremental modernisation.
- 🖼️ Single-spa-style orchestration / route-based composition — each vertical (search, analytics, admin) owned by a team and mounted under its own route, with a shared shell handling auth, navigation, theming, error boundaries and analytics.
- 🏗️ Governance that makes it work — shared design system and tokens, contract-first APIs, common auth/token handling, a cross-team event/communication pattern (custom events or a lightweight bus), independent CI/CD pipelines and versioning, plus observability per remote.
⚖️ I also advise when not to use micro-frontends: for small teams or tightly coupled domains, a modular monolith with a shared component library usually delivers more value with far less operational cost. 🎯 My recommendation is always driven by team topology, deployment independence and the real need for framework heterogeneity.