Micro Frontends Architecture with Module Federation · 课时

宿主应用与远程应用

了解联邦化架构中宿主应用和远程应用的区别及其各自的作用。

宿主应用与远程应用 是 CoddyKit 上的免费 Micro Frontends Architecture with Module Federation 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Micro Frontends Architecture with Module Federation 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Micro Frontends Architecture with Module Federation 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

What are Hosts & Remotes?

In Module Federation, applications play distinct roles: some are hosts, and others are remotes. Think of it like a main stage (host) that invites guest performers (remotes) to share their acts.

This setup allows large applications to be broken down into smaller, independently developed and deployed pieces.

The Host: Your Main App

The Host application is the primary application that boots up first. Its main job is to consume (or load) modules that are exposed by other applications, called Remotes.

It's like the main website that pulls in different widgets or sections from other services.

Host's Key Responsibilities

The Host application has a few crucial responsibilities:

Loading Remotes: It tells Webpack which remote applications it needs to load.
Providing Context: It often provides the overall application shell, routing, and shared dependencies.
Integrating Modules: It renders components or uses functions provided by the remote applications.

The Remote: A Shared Piece

A Remote application is a separate, self-contained application that exposes specific parts of its code for others to consume. It can also consume modules from other remotes (or even act as a host itself!).

These exposed parts could be components, utility functions, or even entire pages.

Remote's Key Responsibilities

The Remote application focuses on:

Developing Features: It builds specific features or UI components independently.
Exposing Modules: It explicitly defines which parts of its codebase can be shared with host applications.
Independent Deployment: It can be built and deployed without affecting the host or other remotes, as long as its exposed interfaces remain consistent.

ModuleFederationPlugin: The Link

Webpack's ModuleFederationPlugin is the magic behind this interaction. Both host and remote applications use this plugin in their Webpack configurations.

It orchestrates how modules are exposed by remotes and consumed by hosts, making them available at runtime.

Remote: Exposing Modules

On the Remote side, you use the exposes property in the ModuleFederationPlugin configuration.

This tells Webpack which files or modules from your remote application should be made available to others.

// webpack.config.js (remote app)
new ModuleFederationPlugin({
  name: 'remoteApp',
  exposes: {
    './Button': './src/Button.js',
    './Header': './src/Header.js'
  }
})

Host: Consuming Remotes

On the Host side, you use the remotes property to declare which remote applications you want to consume from.

You specify a unique name for the remote and its entry point URL.

// webpack.config.js (host app)
new ModuleFederationPlugin({
  name: 'hostApp',
  remotes: {
    remoteApp: 'remoteApp@http://localhost:3001/remoteEntry.js'
  }
})

How They Interact

When the Host application loads, it fetches the remoteEntry.js file from the configured remote URL. This entry file contains a manifest of all modules the remote exposes.

The Host can then dynamically import and use these exposed modules as if they were part of its own codebase.

Quick Check

Which of the following best describes the primary role of a Host application in a Module Federation setup?

Host & Remote Recap

We've learned about the fundamental roles of Host and Remote applications in Module Federation.

Host apps are the main integrators, consuming functionality.
Remote apps are independent units that expose specific modules.

Understanding these roles is key to building scalable micro frontends. Next, we'll dive deeper into setting up your first federated application!

常见问题解答

「宿主应用与远程应用」课时是免费的吗？

是的 — 「宿主应用与远程应用」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Micro Frontends Architecture with Module Federation 课程的其余内容，请升级到 CoddyKit PRO。 Micro Frontends Architecture with Module Federation 课程共包含 4 节课。

「宿主应用与远程应用」这节课中我会学到什么？

了解联邦化架构中宿主应用和远程应用的区别及其各自的作用。你通过在浏览器中直接运行的动手代码来练习 Micro Frontends Architecture with Module Federation，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Micro Frontends Architecture with Module Federation 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Micro Frontends Architecture with Module Federation 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「宿主应用与远程应用」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Micro Frontends Architecture with Module Federation 课中编写并运行代码吗？

能。每节 Micro Frontends Architecture with Module Federation 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Micro Frontends Architecture with Module Federation