Frontend System Design · Lesson 38 of 86 · 4 min
Micro-Frontend Integration Strategies
Your answer here shows if you can balance team autonomy with user experience, a core trade-off in system design.
After you've decided to break up your monolith, you have to put the pieces back together. The integration strategy is the most critical decision in a micro-frontend architecture. It dictates performance, development experience, and how isolated your teams can truly be. In an interview, you need to articulate the trade-offs between the main three options: Module Federation, iframes, and Web Components.
The Core Decision: Isolation vs. Integration
Frame your choice along a single axis: strong isolation versus deep integration. Each strategy represents a point on this spectrum.
Iframes offer maximum isolation. The child application lives in its own world, with its own window object, styles, and framework. This is a hard boundary.
Module Federation offers maximum integration. It allows separate applications, built and deployed independently, to share code at runtime as if they were a single app. This is a soft boundary.
Web Components sit in the middle. They provide component-level encapsulation (Shadow DOM) but live within the host's document and share its global context.
Your job is to pick the right point on the spectrum for the problem at hand.
Module Federation: For a Single, Cohesive App
Module Federation is a Webpack feature that lets you dynamically load code from another, separately deployed application. The "host" app consumes code from a "remote" app.
Its killer feature is sharing dependencies. If the host and remote both use React 18, Module Federation ensures React is only downloaded and initialized once. This avoids the performance penalty of loading multiple frameworks and component libraries, making the final product feel like a single, optimized SPA.
Use it when you want the user experience of a monolith but the development experience of independent teams and deployments. It works best when all teams use a compatible tech stack (e.g., everyone is on React).
The trap: Recommending Module Federation without acknowledging its complexity. It introduces a distributed system at the build/runtime level. Version mismatches in shared dependencies can cause cryptic runtime errors. It's powerful, but it's not free.
Here is a minimal Webpack configuration. One application acts as a remote, exposing a component, while another acts as a host, consuming it.
// products-app (the "remote") webpack.config.js
const { ModuleFederationPlugin } = require('webpack').container;
module.exports = {
//...
plugins: [
new ModuleFederationPlugin({
name: 'products',
filename: 'remoteEntry.js',
exposes: {
'./ProductList': './src/ProductList',
},
shared: { react: { singleton: true }, 'react-dom': { singleton: true } },
}),
],
};
// shell-app (the "host") webpack.config.js
const { ModuleFederationPlugin } = require('webpack').container;
module.exports = {
//...
plugins: [
new ModuleFederationPlugin({
name: 'shell',
remotes: {
products: 'products@http://localhost:8081/remoteEntry.js',
},
shared: { react: { singleton: true }, 'react-dom': { singleton: true } },
}),
],
};
The host can then import the remote component dynamically, often using React.lazy.
// shell-app/src/App.jsx
import React, { Suspense } from 'react';
const ProductList = React.lazy(() => import('products/ProductList'));
function App() {
return (
<div>
<h1>My Application Shell</h1>
<Suspense fallback={<div>Loading...</div>}>
<ProductList />
</Suspense>
</div>
);
}
This diagram shows the core relationship: the host consumes an exposed module from the remote, and both rely on a single, shared instance of their dependencies.
iframes: For Hard Boundaries and Legacy Code
The <iframe> is the oldest and simplest way to compose applications. It embeds a completely separate web page into your own. This creates the strongest possible isolation. The iframe's content cannot affect the parent's CSS or JavaScript, and vice-versa.
This makes iframes the perfect tool for two specific scenarios:
- Integrating legacy systems: You can wrap an old Angular.js or jQuery page in an iframe and drop it into a modern React shell without a full rewrite.
- Embedding untrusted third-party content: This is how services like Stripe, Google Maps, or embedded social media posts work. The isolation is a critical security feature.
The downsides are significant. Iframes are heavy, can create ugly UX seams (like double scrollbars), and make cross-frame communication cumbersome, relying on postMessage. State management and routing across frames are complex.
Interview angle: When you suggest iframes, immediately mention the security model. You must validate the
event.originin yourmessagelistener and specify atargetOriginwhen callingpostMessage. SayingpostMessage(data, '*')in an interview is a red flag.
Web Components: For Universal Building Blocks
Web Components are a set of browser standards for creating framework-agnostic, reusable UI components. Using Custom Elements and the Shadow DOM, you can build something like <my-button> that works in React, Vue, Angular, or plain HTML.
This is not a strategy for integrating entire applications. It's a strategy for creating a shared library of primitive UI elements.
The most powerful use case is for a design system. You can build your company's official button, dropdown, and card components as Web Components. This guarantees visual and functional consistency across projects, even if one team uses Vue and another uses Svelte.
Web Components offer a middle ground on isolation. The Shadow DOM encapsulates the component's styles and markup, preventing global CSS from leaking in. However, the component still lives in the main document and shares the global window object, making integration easier than with an iframe.
Try it
In 15 minutes, sketch out a decision tree for an e-commerce site. The inputs are: the "product recommendations" widget, the "user reviews" section, and the "payment processing" form. The outputs are your chosen integration strategy for each (Module Federation, iframe, or Web Component) with a one-sentence justification.
Next: Now that you know how to assemble micro-frontends, we'll cover how they talk to each other in "Communication Between Micro-Frontends".
Lock it in — apply this lesson under interview conditions.