集中式路由策略
了解单个宿主应用如何为所有集成的微前端管理路由。
集中式路由策略 是 CoddyKit 上的免费 Micro Frontends Architecture with Module Federation 课时。 这是第 1 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Micro Frontends Architecture with Module Federation 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Micro Frontends Architecture with Module Federation 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Intro to Centralized Routing
Welcome to the lesson on Centralized Routing Strategy in Micro Frontends! This approach is crucial for managing navigation across different parts of a large application.
We'll explore how a single 'host' application can take control of all routing decisions, providing a unified user experience.
What is Centralized Routing?
In a centralized routing setup, the main host application (also known as the shell or container) is responsible for defining and managing all routes for the entire application.
- It acts as the single source of truth for navigation.
- It decides which Micro Frontend (MFE) component should be loaded for a given URL path.
- Remote MFEs typically don't manage their own top-level routes.
The Host's Routing Role
Imagine your host application as a traffic controller. When a user navigates to a URL, the host intercepts it, looks at its routing table, and then directs the request to the appropriate Micro Frontend.
The host often uses a routing library (like React Router for React apps) to define these global routes.
Conceptual Host Router Setup
Here's a simplified look at how a host's routing configuration might appear using a popular routing library. Notice how different paths are mapped to components from various Micro Frontends.
import React from 'react';
import { BrowserRouter as Router, Route, Switch } from 'react-router-dom';
// Imagine these are dynamically loaded MFE components
const ProductMFE = React.lazy(() => import('product_app/ProductPage'));
const CartMFE = React.lazy(() => import('cart_app/CartPage'));
const UserProfileMFE = React.lazy(() => import('user_app/ProfilePage'));
const App = () => (
<Router>
<Switch>
<Route path="/products" component={ProductMFE} />
<Route path="/cart" component={CartMFE} />
<Route path="/profile" component={UserProfileMFE} />
<Route path="/" component={HomePage} exact />
</Switch>
</Router>
);
export default App;Dynamic Loading of MFEs
To efficiently load MFEs, the host typically uses dynamic imports. This means an MFE's code is only fetched and loaded when its corresponding route is activated, not upfront when the main application loads.
This improves initial page load times, as users only download the code they need.
Code: Dynamic MFE Import
This snippet shows how React.lazy() combined with Suspense enables dynamic loading and provides a fallback while the MFE component is being fetched.
import React, { Suspense } from 'react';
// Dynamically import a remote component
const RemoteButton = React.lazy(() => import('remoteApp/Button'));
const HostComponent = () => (
<div>
<h1>My Host App</h1>
<Suspense fallback={<div>Loading Remote Button...</div>}>
<RemoteButton label="Click Me!" />
</Suspense>
</div>
);
export default HostComponent;Benefits of Centralized Routing
Adopting a centralized routing strategy offers several key advantages:
- Unified User Experience: Ensures consistent navigation patterns and URLs across the entire application.
- Simplified Global Navigation: Easier to implement a single, cohesive navigation bar or menu.
- Host Control: The host maintains full control over which MFEs are loaded and when.
- Easier Analytics: Centralized routing can simplify tracking user journeys across the entire application.
Considerations and Challenges
While beneficial, centralized routing also has its considerations:
- Host Dependency: The host becomes a critical dependency; if it fails, the entire routing system is down.
- Scalability of Routing Logic: A very large application might make the host's routing configuration complex and difficult to manage.
- MFE Autonomy: Remote MFEs have less control over their own public-facing URLs.
- Version Management: Changes to routes in the host might require coordination with MFE deployments.
When to Use Centralized Routing
This strategy is often ideal for scenarios where:
- A single team or entity owns the overall application shell and navigation.
- The application has a clear hierarchy and a relatively stable set of top-level routes.
- A consistent look and feel across all MFEs is a high priority.
- There's a need for tight integration and shared context across different parts of the application.
Routing Strategy Check
Which of the following are key characteristics or benefits of a Centralized Routing Strategy in Micro Frontends?
Centralized Routing Recap
In this lesson, we explored the Centralized Routing Strategy. We learned that the host application controls all top-level routes, dynamically loading Micro Frontends as needed.
This approach offers benefits like a unified user experience and simplified global navigation, though it introduces a strong dependency on the host. Understanding when to apply this strategy is key to effective Micro Frontend architecture.
用 AI 导师学习 JavaScript — 免费
在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。
- 课程
- 12
- 课程
- 48
常见问题解答
「集中式路由策略」课时是免费的吗？
是的 — 「集中式路由策略」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 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 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 1 节课，共 4 节。
「集中式路由策略」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Micro Frontends Architecture with Module Federation 课中编写并运行代码吗？
能。每节 Micro Frontends Architecture with Module Federation 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。