กลยุทธ์การกำหนดเส้นทางแบบรวมศูนย์

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.

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.

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.

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.

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.

This snippet shows how React.lazy() combined with Suspense enables dynamic loading and provides a fallback while the MFE component is being fetched.

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.

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.

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.

Which of the following are key characteristics or benefits of a Centralized Routing Strategy in Micro Frontends?

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.