Backend Development 19 min read

Principles, Technologies, and Practical Solutions of Live Streaming – A Case Study of Vivo Product Launch

The article outlines core live‑streaming principles, workflow, and major protocols (RTMP, HLS, HTTP‑FLV), then examines Vivo’s product‑launch challenges—massive concurrency, QPS spikes, and content safety—and presents practical solutions such as multi‑level caching, circuit‑breaker degradation, token‑bucket rate limiting to ensure stable, high‑quality streaming.

vivo Internet Technology
vivo Internet Technology
vivo Internet Technology
Principles, Technologies, and Practical Solutions of Live Streaming – A Case Study of Vivo Product Launch

Background

With the rapid development of the live‑streaming industry, live‑streaming technology has become mature. This article introduces the mainstream live‑streaming principles, their application in product‑launch scenarios, and the problems and solutions encountered.

2. Live Streaming Principles

2.1 Streaming Media Technology

Streaming media is audio‑video data that can be continuously received and presented by end users while the provider is still sending it. Two transmission methods exist: download (full file) and streaming (real‑time delivery). The streaming model is analogous to reading a book page by page instead of waiting for the whole document to download.

2.1.1 Types of Streaming

Progressive Streaming : The client downloads the file while watching; only the already downloaded portion can be viewed. It guarantees playback quality and is suitable for on‑demand high‑quality video such as TV programs.

Real‑Time Streaming : Requires matching bandwidth and network conditions, uses dedicated streaming servers and protocols, and supports controls like fast‑forward and rewind. Quality can adapt to the user’s network.

2.1.2 Streaming and Live Broadcast

Streaming technology breaks the bandwidth limitation of traditional “push” media, turning it into a user‑driven “pull” model, which fuels the rapid growth of live‑streaming platforms.

2.2 Live‑Streaming Workflow

The three core roles are:

Broadcaster (push‑end) : Captures audio‑video, processes it (beauty, watermark, filters), encodes & packages it (e.g., H.264/H.265 into MP4, MOV, etc.), and pushes the stream to the server.

Media Server : Receives the stream, performs transcoding, security checks, and forwards the processed stream to a CDN.

Viewer (pull‑end) : Pulls the stream, demultiplexes it into video and audio tracks, decodes (hardware or software), synchronizes audio‑video, and outputs to the display and speakers.

2.3 Live‑Streaming Protocols

Common protocols include RTMP, HLS, and HTTP‑FLV.

2.3.1 RTMP

Real‑Time Messaging Protocol, originally developed by Macromedia/Adobe, supports both push and pull. It packetizes media into chunks, each identified by a Message Stream ID, and reassembles them on the client side.

2.3.2 HLS

HTTP Live Streaming (Apple) slices the live stream into short media segments and provides an M3U8 playlist. The client sequentially pulls the segments via HTTP, making it firewall‑friendly and suitable for large‑scale stable broadcasts.

2.3.3 HTTP‑FLV

HTTP‑FLV encapsulates FLV data over HTTP (port 80), offering better NAT traversal than RTMP.

2.3.4 Protocol Comparison and Selection

Real‑time interaction (e.g., interactive live) prefers RTMP or HTTP‑FLV; stability‑oriented scenarios (e.g., product launch) prefer HLS.

2.4 Summary

The chapter reviews streaming fundamentals and three major protocols, providing a foundation for developers to understand live‑streaming technology.

3. Technical Guarantees for Vivo Product‑Launch Live Stream

3.1 Challenges

Massive concurrent users during the launch cause high QPS, requiring caching, degradation, and rate‑limiting to ensure stability.

3.2 Solutions

3.2.1 Caching : Multi‑level caching (Redis cluster + local cache) reduces pressure on the backend while tolerating brief data inconsistency.

3.2.2 Degradation : When critical services become overloaded, a circuit‑breaker forces fallback to cached data, preserving the core video experience.

3.2.3 Rate Limiting : Token‑bucket algorithm controls bursty traffic such as comment‑lottery requests, ensuring orderly processing.

3.3 Content Safety

Because the live stream is public and interactive, both video and textual content must be screened for prohibited material (e.g., pornographic, political, violent content).

3.4 Summary

Developers must be aware of high‑concurrency challenges, apply caching, degradation, and rate‑limiting, and ensure content safety to deliver a reliable live‑streaming experience.

4. Conclusion

Live streaming now covers many scenarios (product launches, gaming, education, e‑commerce). This article provides a foundational overview; readers are encouraged to explore deeper technical details based on this material.

Live StreamingBackend DevelopmentVideo StreamingHLSRTMPMedia Serverstreaming protocols
vivo Internet Technology
Written by

vivo Internet Technology

Sharing practical vivo Internet technology insights and salon events, plus the latest industry news and hot conferences.

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.