集中型ルーティング戦略
1つのホストアプリケーションで、統合されたすべてのMicro Frontendのルーティングを管理する方法を理解します。
「集中型ルーティング戦略」はCoddyKit上の無料Micro Frontends Architecture with Module Federationレッスンです。 これはレッスン1/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応の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.
よくある質問
「集中型ルーティング戦略」レッスンは無料ですか？
はい。「集中型ルーティング戦略」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Micro Frontends Architecture with Module Federationコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Micro Frontends Architecture with Module Federationコースには全4レッスンが含まれています。
「集中型ルーティング戦略」で何を学びますか？
1つのホストアプリケーションで、統合されたすべてのMicro Frontendのルーティングを管理する方法を理解します。 ブラウザで直接実行するハンズオンコードでMicro Frontends Architecture with Module Federationを演習し、24時間対応の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フィードバックを取得できます。ローカル設定は不要です。