Technical Overview of WeChat Red Packet Distribution System

The piece begins by highlighting the enormous popularity of the Chinese New Year "red‑packet" (hongbao) campaigns, noting that on January 28 the Alipay "Five Blessings" event attracted over 167 million participants and that WeChat reported 142 billion red‑packet transactions on the same day, with a peak of 760,000 packets per second.

It then presents demographic data, showing that users tend to send packets to peers of the same age group, with the 80s, 90s, and 70s generations forming the three most active channels.

From a technical perspective, the article outlines the backend workflow when a user creates an N‑person red‑packet of total amount M yuan. First, a record is inserted into Tencent's CKV distributed key‑value store with an expiration time. The same information is also cached in an internal high‑performance KV service.

When users attempt to claim the packet, the claim operation is performed entirely in the cache layer using an atomic decrement (implemented via a CAS‑style compare‑and‑swap). If the decrement reaches zero, the packet is considered exhausted and further requests are blocked at the cache level, reducing load on the database.

The actual settlement ("opening" the packet) occurs in the database: a transaction updates the number of claimed packets, records the amount taken, and inserts a receipt entry. The amount for each claim is randomly chosen between 1 cent and twice the average remaining amount, with a maximum of M × 2 / N. Settlement throughput is designed for up to 200 k transactions per second, though real traffic peaks at about 80 k per second.

The design separates the high‑frequency claim step from the lower‑frequency settlement step, creating a multi‑layer filtering mechanism that protects the backend from overload and ensures high availability during massive holiday traffic.