Cloud Computing 12 min read

Inside Alibaba Cloud Live Streaming: Architecture, Key Concepts & Best Practices

This article explains the fundamentals of video live streaming, covering terminology, bitrate, frames, key vs. non‑key frames, CDN caching strategies, and the end‑to‑end live streaming pipeline—including capture, preprocessing, encoding, pushing, transcoding, distribution, and playback—along with typical use‑case scenarios.

21CTO
21CTO
21CTO
Inside Alibaba Cloud Live Streaming: Architecture, Key Concepts & Best Practices

Video Basics

Video is a sequence of images displayed at more than 24 frames per second, creating a smooth visual effect. Media transcoding converts audio/video from one encoding format to another. CDN (Content Delivery Network) includes streaming servers, load balancing, routing, transcoding, recording, anti‑hotlinking, and performance optimization.

Key Terminology

Bitrate (kbps) measures data transmitted per unit time; higher bitrate yields higher quality but larger file size. A frame is a single image; key frames can be decoded independently, while non‑key frames depend on preceding frames. Frame rate (fps) indicates frames displayed per second; 30 fps is acceptable, 60 fps feels smoother, but exceeding display refresh rate wastes resources.

Live Streaming Overview

Live streaming delivers video frames with timestamps in a continuous stream. The process includes capture, preprocessing (e.g., beauty filters, watermarks), encoding (hardware vs. software), pushing, transcoding to multiple protocols (RTMP, HLS, FLV), CDN distribution, and client playback. Unlike video‑on‑demand, live streams cannot be fast‑forwarded or rewound.

Live Streaming Architecture

The pipeline consists of:

Capture: devices (iOS, Android, PC/OBS) acquire video.

Pre‑processing: beauty, watermark, blur effects.

Encoding: hardware encoding on iOS, software encoding on Android.

Pushing & Transcoding: RTMP ingestion, conversion to HLS/FLV.

Distribution: CDN nodes provide high‑concurrency delivery.

Client Playback: decoding and rendering on iOS/Android/HTML5.

Push streams use RTMP; playback supports RTMP, HTTP‑FLV, HLS via players such as OBS, VLC, Flash, and HTML5.

Business Functions and Scenarios

Key features include transcoding (quality/bitrate adjustment, watermarks, dynamic templates), periodic screenshots, dynamic configuration, recording, stream authentication, anti‑hotlinking, callbacks, multi‑platform push, audio‑only streams, and comprehensive monitoring of bitrate, traffic, online users, and frame rate to detect network jitter.

Typical use cases:

UGC interactive live (e.g., OneLive, Yingke).

E‑commerce live (e.g., Taobao Live).

Sports events and large‑scale variety shows.

Game live streaming.

Online education and financial live streams.

These solutions enable scalable, reliable live video delivery for a wide range of industries.

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.

cloud computinglive streamingCDNmedia processingVideo Architecture
21CTO
Written by

21CTO

21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.

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.