Databases 7 min read

How Distributed Databases Powered Douyin’s Spring Festival Red‑Envelope Event

In a May 15 meetup, ByteDance engineer Ma Haoxiang discussed his background, the culture at ByteDance, recommended resources, and detailed how distributed databases differ from traditional relational databases, highlighting their massive capacity, low cost, high performance, and the specific performance and disaster‑recovery challenges faced during Douyin’s Spring Festival red‑envelope activity.

Volcano Engine Developer Services
Volcano Engine Developer Services
Volcano Engine Developer Services
How Distributed Databases Powered Douyin’s Spring Festival Red‑Envelope Event

On May 15, the Volcano Engine Developer Community held its second meetup, featuring system development engineer Ma Haoxiang, who shared his experience with distributed databases in Douyin’s Spring Festival red‑envelope activity.

Banner
Banner

Ma introduced himself, noting his master’s degree from Northeastern University, his early fascination with hardware and DOS commands, and his wide range of hobbies such as cooking, art exhibitions, and KTV, which he likens to art.

He joined ByteDance in June 2019 and has been involved in a distributed database system from its inception, now supporting massive traffic across many business lines.

Ma praised ByteDance’s open and humble culture, where both senior and junior engineers can discuss ideas freely.

To stay technically current, his team holds weekly workshops, and he recommends the book Designing Data‑Intensive Applications and recent SIGMOD/VLDB/OSDI/FAST papers for those interested in databases and systems.

Regarding the Spring Festival red‑envelope project, he recalled two memorable moments: the enthusiastic volunteer spirit of the team and the intense testing phase with limited hardware, which required creative performance solutions and extensive contingency plans.

He explained the key differences between distributed databases and traditional single‑node relational databases, highlighting three main characteristics:

Support for massive capacity : Distributed storage allows single tables to reach hundreds of terabytes without complex sharding.

Lower cost and flexible scaling : Compute and storage are decoupled, enabling independent scaling of each layer.

High performance : Scale‑out architecture handles extreme concurrency beyond the limits of a single CPU or disk.

The Spring Festival activity posed two major challenges:

Performance challenge : Extremely high QPS required optimizations to keep query latency low under constrained hardware.

Disaster‑recovery challenge : The system must remain available even if an entire data center fails, demanding multi‑site replication.

Ma summarized the benefits that distributed databases bring to business:

High performance : Provides high transaction throughput under massive concurrency.

Low cost : Allows independent scaling of compute and storage, avoiding waste.

High availability and reliability : Multi‑replica deployment across data centers and stateless compute nodes ensure continuous service.

Speaker
Speaker
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Scalabilitydisaster recoveryhigh performancedistributed databasesSpring FestivalDouyin
Volcano Engine Developer Services
Written by

Volcano Engine Developer Services

The Volcano Engine Developer Community, Volcano Engine's TOD community, connects the platform with developers, offering cutting-edge tech content and diverse events, nurturing a vibrant developer culture, and co-building an open-source ecosystem.

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.