Industry Insights 28 min read

How Meituan Scaled Its Tech Architecture from LAMP to a Cloud‑Native O2O Platform

In this interview, Meituan’s technology committee chair Xia Huaxia explains how the company’s architecture evolved from a simple LAMP stack to a multi‑layer, cloud‑native system, detailing the separation of infrastructure, business, and front‑end components, the use of open‑source tools, and the systematic simplification, standardization, automation, and quantification of business processes to support rapid O2O growth.

Big Data and Microservices
Big Data and Microservices
Big Data and Microservices
How Meituan Scaled Its Tech Architecture from LAMP to a Cloud‑Native O2O Platform

Introduction

Meituan’s technology committee chair Xia Huaxia shares the company’s technical journey, emphasizing that continuous technical effort and a pursuit of excellence are key to Meituan’s success as China’s largest local‑life service platform.

Technical Architecture Evolution

In the early years (2010‑2011) Meituan used a classic LAMP stack: Apache, PHP, MySQL, with basic operations and simple caching (Varnish, Memcached). As traffic grew, the architecture was incrementally optimized, adding Nginx, expanding caching layers, and introducing a mobile API layer in 2011.

Figure 1
Figure 1

When new business lines (hotels, movies, food delivery) were launched, Meituan extracted common, business‑agnostic components (configuration service, queue, registry, SQL/NoSQL storage) into reusable infrastructure services running on a private cloud platform (cloud hosts, storage, virtual networking, load balancers).

Figure 2
Figure 2

Business‑specific components such as user center, payment, search, recommendation, risk control, and geo‑location services were also abstracted into shared services, while the front‑end layer handled request routing, content filtering, and CDN caching.

Business Architecture Optimization

Meituan identified four principles to tame the growing complexity of its business processes:

Simplify complex tasks – remove unnecessary steps and break large workflows into smaller, manageable units.

Standardize simple tasks – define clear specifications, success criteria, and measurement methods for each unit.

Workflow‑ify standards – codify standards into repeatable procedures and manuals for new staff.

Automate workflows – let computers execute the standardized procedures, reducing manual effort.

Applying these principles, Meituan streamlined the “order‑on‑boarding” process. Previously, a contract required manual review, editing, photography, watermarking, and a 7‑10 day turnaround. By digitizing contracts, structuring data fields, and automating validation, the new flow reduced human steps, cut processing time dramatically, and lowered per‑order cost to single‑digit RMB.

Figure 3
Figure 3

O2O Technology Integration

Meituan demonstrated that technology can bridge online and offline operations. For merchants, a cloud‑connected printer receives order details directly from the backend, eliminating phone calls and manual transcription. For users, data‑driven profiling (gender, age, location, device, browsing history) feeds machine‑learning models (e.g., SVM) that predict conversion likelihood, enabling targeted incentives that cut acquisition cost by 35 % and overall spend by 30 %.

Figure 4
Figure 4

Conclusion

The architecture continuously evolves to match business needs: start simple, adopt open‑source components (MySQL, Apache, Lucene, Solr, OpenStack), extract common services, and apply the four optimization principles. By treating both online and offline processes as technical problems, Meituan achieves higher efficiency, lower costs, and a competitive edge in the O2O market.

cloud-nativeopen-sourcebusiness optimizationO2OMeituanTech Architecture
Big Data and Microservices
Written by

Big Data and Microservices

Focused on big data architecture, AI applications, and cloud‑native microservice practices, we dissect the business logic and implementation paths behind cutting‑edge technologies. No obscure theory—only battle‑tested methodologies: from data platform construction to AI engineering deployment, and from distributed system design to enterprise digital transformation.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.