How RocketMQ Transformed Cainiao’s Logistics System for Double‑11 Peaks

Cainiao’s logistics system, originally built on top of Tmall’s shared trading platform, has long been tightly coupled with the e‑commerce core, handling the most critical link of the entire online‑shopping ecosystem.

With the rapid growth of the group’s business and the ever‑increasing order peaks during the annual Double‑11 shopping festival, technical investment and operational costs have surged. In recent years, payment processing capabilities have approached order‑creation speeds, putting additional pressure on the logistics subsystem, whose workload is now directly tied to transaction volume.

Massive Cost Pressure of Double‑11

Analysis of the 2015 Double‑11 peak shows that only a tiny fraction of orders created at midnight were shipped within the first hour, indicating that the logistics side is not driven by its own demand but by the need to keep the transaction‑payment‑logistics chain stable.

Logistics during Double‑11 is driven by document‑based shipping operations, which require substantial human and material resources. The physical nature of shipping does not exhibit sharp traffic spikes, and users care primarily about successful order creation rather than immediate logistics order generation.

Consequently, as transaction order peaks continue to rise each year, the logistics system would need to provision equivalent capacity to maintain synchronous processing—an inefficient and costly approach for a non‑essential scenario. An architectural upgrade of the logistics system became urgent.

RocketMQ—Cainiao Architect’s Choice

Facing the 2016 Double‑11 challenge, architect Wang Wei needed to raise the order‑creation peak from 180 k to 300 k per second. He decided to adopt RocketMQ, Alibaba’s widely used distributed messaging middleware, to decouple the transaction and logistics domains.

RocketMQ, battle‑tested through multiple Double‑11 events, offers world‑leading performance, supporting billions of messages with precise flow‑control capabilities. By using RocketMQ for asynchronous decoupling, the logistics order center can consume transaction traffic at a controlled rate (e.g., 80 k /s) while the transaction side peaks at 500 k /s, allowing the backlog to be processed over a longer period without user impact.

This approach dramatically reduces the need for additional hardware, cuts labor and material costs, and eliminates stability risks associated with synchronous dependencies. After two months of development, testing, and gradual rollout before Double‑11 2016, the logistics system’s peak QPS remained unchanged despite a four‑fold increase in transaction peaks, saving substantial technical costs and laying a foundation for future cost reductions.