How MaFengWo Built a Scalable Marketing Platform for Double‑11: Architecture Insights
This article details the design and implementation of MaFengWo's marketing platform for the Double‑11 travel promotion, covering its modular architecture, data layer, flexible development model, reliability mechanisms, and future roadmap to support high‑traffic, secure, and maintainable marketing activities.
Introduction
After the recent Double 11 shopping festival, MaFengWo faced increasing technical demands to support not only promotional battles but also complex marketing operations. Over five years, the company has run more than 50 major promotional events and hundreds of smaller activities each year.
Marketing Platform Architecture
The platform is divided into B‑side (merchant) and C‑side (consumer) components. B‑side helps merchants submit and select promotional items, while C‑side enables users to participate in activities such as flash sales, red‑packet grabs, and coupons.
1. Marketing Center System
Key capabilities required are:
Flexible and efficient activity development
High reliability and availability
Secure operation of marketing activities
To achieve this, the system follows a platform‑centric, component‑centric, and module‑centric approach.
2. C‑Side Marketing Platform
The C‑side architecture consists of four layers:
Activity Development Platform : core layer, including three subsystems – "Magic Cube" (frontend page builder), "Bee Playground" (business logic), and "Prize Pool" (reward rules).
Delivery Platform : handles activity page placement, strategies, and mechanisms.
Middleware : provides concurrency control, distributed caching, and rate‑limiting.
Marketing Applications : includes large‑scale promotions, business marketing, and newcomer gift packs.
2.1 Flexible and Efficient Development Model
The data pool underlying the platform is built with MySQL, ElasticSearch, and Redis:
request:
-
field: deviceId
rule: required # required field validation
method: post
message: deviceId parameter error
-
field: sex
rule: in:[0,1] # range validation
method: post
message: gender range error
-
field: phone
rule: regex:/^1[3456789]\d{9}$/ # regex validation
method: post
message: phone number format errorConfiguration modules (e.g., parameter configuration, validator, executor, and reward service) are defined in YAML and loaded at runtime, allowing tasks to be assembled from reusable components.
2.2 Prize Pool
The Prize Pool abstracts the lifecycle of reward distribution, supporting creation of prize pools, setting prize items, user draws, and statistics. Initially implemented with a simple relational table, it was later redesigned using Redis Sorted Sets to evenly distribute prize issuance over the activity period and prevent premature depletion.
2.3 Availability, Reliability, and Risk Control
High‑traffic scenarios such as flash sales employ rate‑limiting and traffic‑shaping techniques. The system uses RabbitMQ to buffer spikes, Redis tokens to prevent overselling, and plans to integrate Sentinel/Hystrix for circuit‑breaking. A unified risk‑control center validates user eligibility before reward issuance.
Future Plans
Upcoming improvements include a comprehensive monitoring system for real‑time activity metrics, migration from a monolithic to a micro‑service architecture, and continued enhancements to reliability and risk management.
Conclusion
Continuous abstraction and refactoring of the marketing platform enable MaFengWo to support increasingly complex and engaging promotional activities while maintaining high performance, security, and developer efficiency.
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.
Mafengwo Technology
External communication platform of the Mafengwo Technology team, regularly sharing articles on advanced tech practices, tech exchange events, and recruitment.
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.
