Backend Development 2 min read

Design of a High-Concurrency Virtual Item Trading System

Meipai’s virtual‑item trading system, built to support over 100,000 daily live streams and millions of concurrent viewers, must process tens of thousands of requests per second while guaranteeing strong data consistency and high availability, and this talk by technical director Guo Chenhui explains the key design choices and trade‑offs employed.

Meitu Technology
Meitu Technology
Meitu Technology
Design of a High-Concurrency Virtual Item Trading System

Meipai generates over 100,000 live streams per day, creating massive volumes of virtual item transactions. During star live streams (e.g., TFBoys), concurrent viewers can reach the million‑level, putting extreme pressure on the transaction system.

The virtual‑item trading system is a core component of Meipai’s commercialization platform, supporting live‑streaming services. It must handle tens of thousands of concurrent requests per second, ensure strong data consistency under high load, and maintain high availability.

This presentation shares the design decisions and trade‑offs made by Meipai when building a high‑concurrency item trading system.

Speaker: Guo Chenhui – Technical Director of Meipai Business Unit, Meitu.

Guo joined Meipai in 2014 and now leads the overall technical architecture, including unified account system, multi‑IDC migration, and other platform initiatives.

Download the full PPT (extraction code: s4rw) from the original article.

backend architecturelive streamingsystem designhigh concurrencytrading system
Meitu Technology
Written by

Meitu Technology

Curating Meitu's technical expertise, valuable case studies, and innovation insights. We deliver quality technical content to foster knowledge sharing between Meitu's tech team and outstanding developers worldwide.

0 followers
Reader feedback

How this landed with the community

login 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.