Official source
The Art of Micro Frontends - Second Edition
A book about scaling micro-frontend platforms in enterprises: from orchestration and governance to developer experience.
The Art of Micro Frontends - Second Edition
Authors: Florian Rappl
Publisher: Packt Publishing
Length: 356 pages
Florian Rappl on mature micro-frontends practices: orchestration, communication, governance, developer experience and enterprise case studies.
OriginalWhat is this book about?
The second edition focuses on operational maturity micro-frontends: how to build a platform that scales with teams and does not fall apart as the number of modules, releases and integration dependencies grows.
Key Focuses
Runtime Orchestration
How a shell component manages the booting, isolation, and lifecycle of microfrontends without becoming a monolithic bottleneck.
Communication Contracts
Patterns of interaction between independent modules: events, shared state boundary and contract integration.
Governance at Scale
How to maintain a balance between team autonomy and a single quality bar for security, UX and reliability.
Developer Experience
Local development, testing, observability and platform tools for fast, secure delivery.
Architectural lenses
- Domain-first decomposition: boundaries by business capabilities, not by frameworks.
- Composable platform layer: routing, identity, telemetry, design system as a common contract.
- Explicit integration model: publish/subscribe, API contracts, interface version.
- Operational readiness: error budgets, rollback strategy, compatibility matrix.
Practical rollout checklist
- Fix the ownership and interfaces of domain modules before starting the migration.
- Collect platform capabilities: auth, navigation, monitoring, release pipelines.
- Implement integration tests between micro-frontends and shell.
- Define governance process for shared contracts and breaking changes.
- Gradually transfer critical user flows to the new model.
What should be in a platform team
Core capabilities
- Release orchestration and rollback automation.
- Compatible telemetry stack for all domain modules.
- Contract registry and version control lifecycle.
Engineering process
- RFC/ADR process for platform-level changes.
- Quality gates before publishing modules in production.
- Automatic compatibility checks between releases.
Antipatterns
- Cross-team shared state without a clear ownership and versioning model.
- Strong connectivity of modules through internal informal dependencies.
- Lack of contract tests at the boundaries of micro-frontends.
- A platform without an owner team and SLO for developer tooling.
- Ignoring UX consistency in favor of complete technological freedom.