Blog
Field notes on micro frontend architecture: Module Federation, versioning across environments, canary releases and rollbacks, from the team building it.
Do you actually need micro frontends?
Micro frontends solve an organisational problem before a technical one. If you do not have that problem, they mostly add work. An honest checklist.
Module Federation with Vite in production: what changes
Module Federation works with Vite, but dev and build take different paths, and the gap is where production surprises come from. What to expect.
One build, every environment: runtime configuration for micro frontends
If your pipeline builds the same code once per environment, the artifact you tested is not the artifact you ship. Here is how to build once instead.
How to roll back a micro frontend in 30 seconds (without rebuilding the host)
A bad release is live and the clock is running. Most teams need fifteen minutes to undo it, because the version is baked into the host build. It need not be.
Deterministic AI Agents in Mission-Critical Systems: Why Microfrontend Boundaries Matter
Learn how microfrontend architecture creates natural safety boundaries for AI agents in production. Reduce blast radius, increase determinism, and deploy AI reliably.
How to Ship Canary Releases for Microfrontends Without Losing Your Mind
Canary releases for MFEs are complex. Learn how they work, why DIY is painful, and how to implement them safely—step by step.
Federation Solved Composition. Nobody Solved Deployment Reliability
Why Module Federation doesn't solve deployment reliability. The gap every MFE team rebuilds: canary releases, rollback, and safe deployments. What's missing from your stack
Also available as an RSS feed.