核心概念与原则

Now the core principles behind effective Micro Frontends — the blueprint for building scalable, maintainable, and flexible web apps.

Independent Deployability means each MFE ships on its own. A change to Product Details never forces a Shopping Cart redeploy, so teams release freely.

Technology Agnosticism lets each team choose its own stack — React for one MFE, Vue for another — using the best tools and dodging framework lock-in.

Isolation prevents conflicts: scope CSS so styles do not leak, isolate JavaScript to avoid global clashes, and give each MFE its own DOM area.

Vertical Slicing splits by business capability, not layer — each slice owns its UI down to its backend and data, aligning teams with domains.

MFEs thrive on autonomous teams: each small team owns an MFE's full lifecycle, which builds expertise, speeds decisions, and cuts cross-team chatter.

Composition is how independent MFEs form one UI. It can happen client-side in the browser, server-side before sending, or edge-side at the CDN.

Composition timing matters: build-time bundles MFEs into one artifact (less dynamic), while runtime loads them in the browser for more flexibility.

Shared dependencies like React or a design system should load once, not per MFE. The principle: share common libraries efficiently across all of them.

Which of the following are core principles of Micro Frontend architecture?

Recap of the core principles: independent deployability, tech agnosticism, isolation, vertical slicing, composition, and shared dependencies. Next: Module Federation.