The Future of Micro-Frontends: How to Combine Module Federation with Server-Side Rendering (SSR)
Client-side Module Federation has a well-known weakness, the browser downloads a shell, then fetches...
Tag archive
Client-side Module Federation has a well-known weakness, the browser downloads a shell, then fetches...
What Are Micro-Frontends? Micro-frontends represent an architectural pattern where a large...
The account team releases its new frontend. The shell stays on the previous version. Checkout was...

Hace unos meses me tocó llevar una plataforma corporativa a una arquitectura de microfrontends: un...

Two micro-frontends, two repos, one patch version apart. Nothing failed until production loaded them together. Here is why, and how to catch it in CI.
Part 6 of an 8-part series on Native Federation v4 for enterprise architecture teams. New to the...

This is part of my series "My Open-Source Projects", where I walk through the projects I started or...
Clear, practical explanations of MVVM, micro‑frontends, and domain‑driven design for modern React/Next.js teams, with examples, folder structures, and trade‑offs.

How canary releases work for microfrontends, why building them yourself hurts, and how to roll one out safely, step by step.

How microfrontend boundaries contain what an AI agent can break in production: smaller blast radius, more determinism, and safer deploys.

Module Federation on Vite works, but dev and build behave differently. Where that gap shows up in production, and what to check before it does.

Why Module Federation doesn't solve deployment reliability. The gap every MFE team rebuilds: canary releases, rollback, and safe deployments.