Penerapan Perutean Federasi
Terapkan perutean yang memungkinkan setiap frontend mikro mengelola rutenya sendiri dan mengintegrasikannya ke dalam perute global.
Penerapan Perutean Federasi adalah pelajaran Micro Frontends Architecture with Module Federation gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Micro Frontends Architecture with Module Federation, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Micro Frontends Architecture with Module Federation mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
What is Federated Routing?
In a Micro Frontend (MFE) architecture, federated routing means each individual MFE is responsible for managing its own specific routes. Instead of one central application dictating all routes, each MFE declares its own pathways.
This approach gives teams more autonomy, allowing them to develop and deploy routing logic independently without tightly coupling to a main host application's routing system.
Benefits of Federated Routes
Federated routing offers several key advantages:
- Autonomy: MFE teams control their own navigation.
- Independent Deployment: Changes to an MFE's routes don't require redeploying the entire host app.
- Scalability: Easier to manage routing logic as the number of MFEs grows.
- Technology Agnostic: Different MFEs can use different routing libraries.
Core Principle: Route Ownership
The fundamental idea behind federated routing is that each Micro Frontend publishes its own set of routes. Think of it like a mini-application within the larger system, responsible for its internal navigation structure.
The host application then acts as an aggregator, discovering and integrating these MFE-owned routes into a single, cohesive routing experience for the user.
MFE Defining Local Routes
Here's how a Micro Frontend (let's call it "MFE A") might define its internal routes. These are specific paths that MFE A is responsible for rendering.
We're using a simple array structure to represent routes, where each route has a path and a component or view it should render.
// mfe-a-routes.js
// This MFE owns routes starting with '/app-a'
export const mfeARoutes = [
{
path: '/app-a',
component: 'MFE_A_Dashboard'
},
{
path: '/app-a/profile',
component: 'MFE_A_UserProfile'
}
];Another MFE's Routes
Similarly, another Micro Frontend ("MFE B") will define its own set of routes. Notice how its paths are distinct, often prefixed to avoid conflicts, ensuring clear ownership.
This separation allows MFE A and MFE B to evolve their navigation independently.
// mfe-b-routes.js
// This MFE owns routes starting with '/app-b'
export const mfeBRoutes = [
{
path: '/app-b',
component: 'MFE_B_HomePage'
},
{
path: '/app-b/settings',
component: 'MFE_B_SettingsPage'
}
];Host Aggregates MFE Routes
The host application's role is to act as the central orchestrator. It needs to discover and import the route definitions provided by each Micro Frontend.
Using Module Federation, these route definitions can be exposed by remote MFEs and consumed by the host, effectively building a global route map from distributed sources.
Integrating into a Global Router
The host application then takes all the aggregated routes and integrates them into its own global router instance. This example simulates how a host app might load and process routes from different MFEs to handle navigation.
Try changing the currentPath variable in the code and run it!
// mfe-a-routes.js (Simulated Remote MFE)
export const mfeARoutes = [
{ path: '/app-a', component: 'MFE_A_Dashboard' },
{ path: '/app-a/profile', component: 'MFE_A_UserProfile' }
];
// mfe-b-routes.js (Simulated Remote MFE)
export const mfeBRoutes = [
{ path: '/app-b', component: 'MFE_B_HomePage' },
{ path: '/app-b/settings', component: 'MFE_B_SettingsPage' }
];
// host-app.js (Main Application Entry Point)
// In a real app, these would be dynamically imported
// via Module Federation.
const allFederatedRoutes = [
...mfeARoutes,
...mfeBRoutes
];
function globalRouter(currentPath) {
console.log(`Attempting to navigate to: ${currentPath}`);
const matchedRoute = allFederatedRoutes.find(
route => route.path === currentPath
);
if (matchedRoute) {
console.log(`Match found! Rendering: ${matchedRoute.component}`);
} else {
console.log(`No route found for: ${currentPath}. Showing 404.`);
}
}
// Simulate user navigation
console.log("--- Global Routing Simulation ---");
globalRouter('/app-a');
globalRouter('/app-b/settings');
globalRouter('/app-a/profile');
globalRouter('/unknown-path');
globalRouter('/app-b');Seamless Cross-MFE Navigation
Once the host's global router has integrated all federated routes, navigation between different Micro Frontends becomes seamless. From the user's perspective, it feels like a single, unified application.
When a user clicks a link to /app-b/settings, the global router identifies that this path belongs to MFE B and delegates the rendering or activation of MFE B accordingly.
Avoiding Route Conflicts
With multiple MFEs defining routes, conflicts can arise if two MFEs define the same path (e.g., both have a /dashboard route).
Common strategies to prevent this include:
- Namespacing: Prefixing MFE routes (e.g.,
/mfea/dashboard,/mfeb/dashboard). - Unique Paths: Ensuring each MFE's routes are inherently unique.
- Host Override: Allowing the host to prioritize or remap conflicting routes.
Check Your Understanding
Imagine you have a host application integrating routes from two Micro Frontends, MFE-A and MFE-B. MFE-A defines /products and /products/:id. MFE-B defines /cart and /checkout.
Which of the following best describes the host application's role in this federated routing setup?
Recap: Federated Routing
You've learned about federated routing, where each Micro Frontend owns and defines its own routes. We saw how a host application aggregates these routes to create a unified navigation experience.
- Each MFE declares its own routes.
- Host app collects and integrates MFE routes.
- Ensures MFE autonomy and independent deployment.
- Namespacing helps prevent conflicts.
This approach is crucial for large-scale MFE systems, balancing independence with a consistent user experience.
Belajar JavaScript dengan tutor AI — gratis
Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.
- Kursus
- 12
- Pelajaran
- 48
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Penerapan Perutean Federasi” gratis?
Ya — teks lengkap “Penerapan Perutean Federasi” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Micro Frontends Architecture with Module Federation, upgrade ke CoddyKit PRO. Kursus Micro Frontends Architecture with Module Federation mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Penerapan Perutean Federasi”?
Terapkan perutean yang memungkinkan setiap frontend mikro mengelola rutenya sendiri dan mengintegrasikannya ke dalam perute global. Kamu berlatih Micro Frontends Architecture with Module Federation dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Micro Frontends Architecture with Module Federation?
Tidak diperlukan pengalaman sebelumnya. Micro Frontends Architecture with Module Federation di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.
Berapa lama pelajaran “Penerapan Perutean Federasi” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Micro Frontends Architecture with Module Federation ini?
Ya. Setiap pelajaran Micro Frontends Architecture with Module Federation menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Strategi Perutean Terpusat
- Penerapan Perutean Federasi
- Tautan Mendalam dan Pengelolaan URL
- Menangani Navigasi Bersarang dan Lintas Aplikasi