This article examines why micro‑frontend architecture is needed for large monolithic front‑end apps and workbench scenarios, compares SPA/MPA, iframe and shared component approaches, and details icestark’s core concepts, routing, communication, isolation techniques and micro‑module integration.
This article presents a comprehensive technical study on adopting micro‑frontend architecture to solve version‑dependency, resource‑size, and navigation‑performance issues in a large internal system suite, detailing background analysis, solution research, layered architecture design, key technical challenges, custom webpack plugins, build workflow, and remaining open problems.
This article explains how Alibaba Cloud’s ConsoleOS implements a JavaScript and CSS sandbox for micro‑frontend applications, covering the underlying principles, code examples, native object simulation via iframes, CSS isolation techniques, and integration tips for other micro‑frontend frameworks.
This article examines the technical evolution of Alibaba's DataWorks platform, detailing the pain points of a monolithic IDE, the transition through componentization, and the adoption of micro‑frontend and plugin architectures to achieve flexible, scalable, and maintainable big‑data development tooling.
This article explores the challenges of component maintenance in micro‑frontend architectures, compares different component types, and presents a practical CLI tool that automates scaffolding, testing, documentation, and publishing to streamline the creation of a reusable, well‑documented component library.
Vivo’s Wukong Activity Middle Platform employs a micro‑frontend RSC architecture to streamline marketing H5 development by providing reusable components, template and task marketplaces, real‑time cloud configuration, asset libraries, and PaaS developer tools—including a VSCode plugin—reducing release cycles, resource waste, data silos, and security risks across 30+ business units.
The article introduces Bifrost, Meituan’s Vue‑based micro‑frontend framework, detailing its background, design goals, architecture, implementation code, development practices, deployment workflow, and the benefits and challenges of adopting micro‑frontend architecture in large‑scale enterprise front‑end projects.
Meituan Waimai’s advertising team tackled duplicated business logic and slow builds across PC, H5, and KA by merging code into a monorepo and adopting a React‑based central‑router micro‑frontend architecture, where a host app dynamically loads sub‑apps with independent routing, stores, CSS, and hot‑module replacement, achieving modularization, faster builds, and isolated deployment.
This article explains the background, core concepts, advantages, and various implementation approaches of micro frontends, and provides a step‑by‑step guide—including project setup, configuration, communication, and optimization—using Vue, single‑spa, and related tools.
The iQIYI front‑end team built a Vue‑based micro‑frontend framework where a lightweight container supplies shared Vue, router and store globals, dynamically loads each module’s manifest‑listed scripts, merges their routes, and renders them via global functions, yielding a decoupled, maintainable, and extensible application architecture.
This article explains how micro‑frontend architecture tackles the maintainability challenges of monolithic front‑ends, outlines its three core business values, details ten technical problems it must solve, and shows the essential infrastructure, configuration, and observability components needed for cloud‑era web development.
Meituan's R&D built Bifrost, a micro‑frontend framework that splits a monolithic Vue SPA into independent sub‑systems, letting remote teams develop, deploy, and integrate modules while preserving a seamless SPA experience; the host manages lifecycle, routing, shared state, CDN delivery, gray releases, and monitoring, greatly improving scalability and maintainability.
This article details NetEase Yanxuan's enterprise micro‑frontend solution, covering its architectural design, isolation techniques, communication mechanisms, configuration center, and the concrete business benefits such as breaking down giant monoliths, improving module reuse, and streamlining multi‑team collaboration.
The article summarizes Chen Cheng's 2019 InfoQ talk on Ant Financial's frontend framework evolution—from early Sea.JS and Arale to Umi and Bigfish—detailing the merged architecture, plugin system, asset market, micro‑frontend strategy, routing, performance optimizations, testing, monitoring, and future plans.
By applying micro‑frontend principles and DDD‑based microservice design, the article explains how insurance companies can build modular, reusable front‑end components that integrate with backend middle‑platform services, thereby lowering integration complexity, improving scalability, and enabling unified, cross‑product order sales across multiple channels.
The article describes how Meituan applied the micro‑frontend concept to transform its HR system into a class‑single‑page application, detailing the shortcomings of iframe integration, the design of a portal project, application registration, routing, CSS scoping, JavaScript library version control, and the build‑and‑deployment workflow.
Meituan’s HR platform adopts a micro‑frontend architecture where a central Portal container registers isolated sub‑projects via a global route array, namespaces CSS, unifies shared libraries through a custom require system, and deploys static assets with PM2, delivering a single‑page experience, independent releases, and minimal bundle overhead.