-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path26_Micro_Frontend.js
More file actions
22 lines (22 loc) · 919 Bytes
/
26_Micro_Frontend.js
File metadata and controls
22 lines (22 loc) · 919 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
/**
* 26. What is Micro-Frontend Architecture?
*
* Concept:
* - Applying the Microservices concept to the Frontend.
* - Instead of a giant "Monolith" React app managed by 50 developers, you split the UI into smaller, vertical apps (e.g., "Checkout Team", "Search Team", "User Profile Team").
*
* Implementation Styles:
* 1. Build-time integration: Publishing components as NPM packages (slow).
* 2. Run-time integration: Using IFrames (strong isolation, hard communication).
* 3. Run-time integration (JS): Webpack Module Federation (current standard). Hosting shell app that loads fragments.
*
* Pros:
* - Independent deployments (Team A doesn't break Team B).
* - Technology agnostic (Team A uses React, Team B uses Vue - though risky for bundle size).
* - Scalability.
*
* Cons:
* - Complex infrastructure.
* - Shared dependencies management.
* - Inconsistent UI/UX if not governed strictly.
*/