Meituan Waimai Mobile Architecture Evolution and Containerization
Meituan Waimai’s mobile architecture progressed from early componentization through platformization and a custom React‑Native hybrid to a containerized system that unifies Android and iOS via SDKs, MRN and Titans containers, enabling dynamic updates, modular development, and massive traffic handling while demanding enhanced monitoring and release governance.
The article describes how Meituan’s most important business, Meituan Waimai (food delivery), has continuously evolved its mobile architecture to keep up with rapid business growth.
1. Background
Mobile cross‑platform technologies such as WebView containers, React Native, Weex, Flutter and mini‑programs have long been used to reduce development cost by enabling one‑code‑base to run on both Android and iOS. The article briefly introduces WebView, React Native and Flutter, highlighting their principles, advantages and limitations.
2. Meituan Waimai Business Overview
Meituan Waimai is a complex e‑commerce platform covering dozens of food categories and multiple entry points (stand‑alone app, Meituan app channel, Dianping app channel). Its complexity creates significant architectural challenges.
3. Historical Architecture Evolution
• Componentization (2013‑2015) : Early native code was duplicated across apps, leading to high coupling. The goal was to split the system into independent reusable components.
• Platformization (2015‑2017) : A shell container and a platform‑ability layer were introduced to enable multi‑app reuse and support growing teams and features.
• RN Hybrid (2017‑2018) : Meituan built its own MRN (Meituan React Native) framework, customizing scaffolding, component libraries, pre‑loading and deployment to improve development efficiency and reduce app size.
• Containerization (2019‑present) : The current architecture abstracts the front‑end environment into standardized containers, separating business modules from the host app and supporting dynamic, remote‑driven updates.
4. Containerization Architecture Overview
The container layer sits above system services and internal infrastructure, providing a unified SDK that hides platform differences. It supports three page categories: high‑PV core pages (partial dynamic modules), low‑PV auxiliary pages (MRN containers), and fast‑changing activity pages (WebView‑based Titans containers).
5. Advantages
• Dynamic updates without app recompilation, reducing compile time from seconds to milliseconds. • Unified SDK improves development efficiency across Android and iOS. • Standardized interfaces enforce consistency and enable fine‑grained modularization. • Better monitoring of download, loading and usage links.
6. Challenges
• Maintaining consistency across multiple host apps and platforms. • Introducing a new “dynamic release” lifecycle alongside traditional app releases. • Monitoring and ensuring reliability of the longer execution chain introduced by containers.
7. Key Container Implementations
• MRN Container : An enhanced React Native runtime that adds containerization, dynamic delivery, multi‑app reuse and engineering safeguards. Over 40 Meituan apps and 100+ contributors use MRN, serving billions of page views.
• Roo Component Library : A standardized UI component set built on top of MRN to unify design and improve development speed.
• Titans Container : A unified WebView‑based container that standardizes UI, navigation, bridge protocols (KNB) and provides pre‑loaded resources for fast page rendering.
8. Page Containerization Design
The design proceeds in three stages: module ordering (splitting coupled code into independent modules), module orchestration (config‑driven layout and AB‑testing), and progressive rollout (gradually migrating native modules to dynamic Mach modules).
9. Monitoring & Operations
Metrics are divided into download, loading and usage links, with key indicators such as bundle download success rate, bundle load success rate, JS error rate, crash rate, etc. Real‑time alerts, dashboards and automated testing are used to ensure container reliability.
10. Release Process
Release includes three dimensions: content (pages or modules), configuration (AB‑test, style, feature flags) and bundle resources (MRN/Mach bundles). A multi‑stage pipeline (test → gray → full) with SOP checks, leader/QA approval and time‑window constraints ensures safe deployment.
11. Conclusion
Containerization has enabled Meituan Waimai to handle massive traffic (peak >40 million orders per day), support rapid feature iteration, reduce app size, and improve developer productivity, while introducing new requirements for monitoring, testing and release governance.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Meituan Technology Team
Over 10,000 engineers powering China’s leading lifestyle services e‑commerce platform. Supporting hundreds of millions of consumers, millions of merchants across 2,000+ industries. This is the public channel for the tech teams behind Meituan, Dianping, Meituan Waimai, Meituan Select, and related services.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
