Why video streaming handles massive data in HLD - Design It to Understand It

Design: Video Streaming Data Handling

Focus on data handling aspects of video streaming including storage, delivery, and scaling. Exclude detailed UI design and content creation.

Functional Requirements

FR1: Support streaming of video content to millions of users simultaneously

FR2: Deliver video with minimal buffering and latency

FR3: Handle different video qualities and formats

FR4: Allow users to pause, rewind, and fast-forward videos

FR5: Support live streaming and on-demand videos

Non-Functional Requirements

NFR1: Scale to handle millions of concurrent viewers

NFR2: Maintain p99 latency under 300ms for video start time

NFR3: Ensure 99.9% availability for streaming service

NFR4: Efficiently store and serve large video files

NFR5: Optimize bandwidth usage to reduce costs

Think Before You Design

Questions to Ask

❓ Question 1

❓ Question 2

❓ Question 3

❓ Question 4

❓ Question 5

Key Components

Video storage system (object storage or distributed file system)

Content Delivery Network (CDN)

Video encoding and transcoding services

Load balancers and streaming servers

Caching layers and edge servers

Design Patterns

Content Delivery Network (CDN) for caching and distribution

Adaptive Bitrate Streaming to adjust video quality dynamically

Sharding and partitioning of video data

Asynchronous processing for encoding and uploading

Load balancing for streaming servers

Reference Architecture

User Devices
   |
   v
Load Balancer
   |
Streaming Servers <--> Video Encoding Service
   |
CDN Edge Servers
   |
Distributed Video Storage

Components

Load Balancer

Nginx or AWS ELB

Distributes user requests evenly to streaming servers

Streaming Servers

Custom streaming server or Wowza

Handles video streaming sessions and user controls

Video Encoding Service

FFmpeg or cloud encoding services

Transcodes videos into multiple formats and bitrates

Content Delivery Network (CDN)

Cloudflare, Akamai, AWS CloudFront

Caches video content close to users to reduce latency

Distributed Video Storage

Amazon S3, Google Cloud Storage, or HDFS

Stores original and transcoded video files reliably

Request Flow

1. User requests video from device.

2. Request hits Load Balancer which routes to Streaming Server.

3. Streaming Server checks CDN cache for requested video segment.

4. If cache miss, Streaming Server fetches video segment from Distributed Video Storage.

5. Video segment delivered to CDN edge server and then to user device.

6. Video Encoding Service processes uploaded videos into multiple qualities asynchronously.

7. CDN caches popular video segments to serve future requests quickly.

Database Schema

Entities: - Video: id, title, description, upload_date, duration - VideoSegment: id, video_id (FK), quality, format, storage_path - User: id, username, subscription_type - StreamingSession: id, user_id (FK), video_id (FK), start_time, end_time Relationships: - One Video has many VideoSegments - One User can have many StreamingSessions - StreamingSessions link Users to Videos watched

Scaling Discussion

Bottlenecks

Storage capacity and throughput for large video files

Network bandwidth for streaming to many users

Encoding service processing time for new videos

Load on streaming servers during peak usage

Cache misses causing higher latency

Solutions

Use scalable object storage with automatic replication and partitioning

Deploy CDN with global edge locations to reduce bandwidth load on origin

Use distributed and parallel encoding pipelines

Auto-scale streaming servers based on traffic

Pre-warm CDN caches and use predictive caching algorithms

Interview Tips

Time: 10 minutes to clarify requirements and constraints, 15 minutes to design architecture and data flow, 10 minutes to discuss scaling and bottlenecks, 10 minutes for Q&A

Explain why video data is massive due to size and concurrent users

Discuss importance of CDN to reduce latency and bandwidth

Highlight adaptive bitrate streaming for user experience

Mention asynchronous encoding to handle large uploads

Describe scaling strategies for storage, network, and compute

Practice

1. Why does video streaming handle massive data in system design?

easy

A. Because it uses very little bandwidth

B. Because it stores only small text files

C. Because it sends large video files to many users at the same time

D. Because it only streams audio files

Solution

1. Step 1: Understand video file size and user demand

   Video files are large and streaming means sending these files to many users simultaneously, increasing data volume.

2. Step 2: Connect streaming to data volume

   Because many users watch videos at once, the system must handle massive data to serve all without delay.

3. Final Answer:

   Because it sends large video files to many users at the same time -> Option C

4. Quick Check:

   Large files + many users = massive data [OK]

Hint: Think about file size and number of viewers together [OK]

Common Mistakes:

• Confusing video with small text data
• Ignoring simultaneous user connections
• Assuming streaming uses little bandwidth

2. Which component is essential in video streaming to reduce data size before sending?

easy

A. Compression algorithms

B. Database indexing

C. Load balancers

D. Firewall rules

Solution

1. Step 1: Identify data size reduction methods

   Compression algorithms reduce the size of video files to save bandwidth and speed up delivery.

2. Step 2: Match components to their roles

   Load balancers and firewalls manage traffic and security but do not reduce data size; database indexing is unrelated to video size.

3. Final Answer:

   Compression algorithms -> Option A

4. Quick Check:

   Compression reduces file size [OK]

Hint: Compression shrinks files before sending [OK]

Common Mistakes:

• Confusing load balancers with compression
• Thinking firewalls reduce data size
• Mixing database indexing with streaming data size

3. Consider a video streaming system using CDN. What is the main benefit of CDN in handling massive data?

medium

A. It converts videos to text for faster delivery

B. It compresses videos on the user device

C. It blocks unauthorized users from streaming

D. It stores copies of videos closer to users to reduce latency

Solution

1. Step 1: Understand CDN role in streaming

   CDNs store copies of video content on servers near users to reduce the distance data travels, lowering delay and bandwidth use.

2. Step 2: Eliminate incorrect options

   Compression happens before CDN; blocking users is security, not data handling; converting videos to text is not practical.

3. Final Answer:

   It stores copies of videos closer to users to reduce latency -> Option D

4. Quick Check:

   CDN = closer storage for faster delivery [OK]

Hint: CDN means closer servers to users [OK]

Common Mistakes:

• Thinking CDN compresses videos on devices
• Confusing CDN with security features
• Imagining videos converted to text

4. A video streaming system is buffering a lot despite using compression and CDN. What is a likely cause?

medium

A. Too much compression causing video corruption

B. Insufficient network bandwidth between CDN and users

C. CDN servers are too close to users

D. Users have too many devices connected

Solution

1. Step 1: Analyze buffering despite compression and CDN

   If buffering happens, it often means data can't reach users fast enough, likely due to network bandwidth limits.

2. Step 2: Evaluate other options

   Too much compression usually reduces quality but not buffering; CDN too close is good; user devices count affects local network, not streaming server.

3. Final Answer:

   Insufficient network bandwidth between CDN and users -> Option B

4. Quick Check:

   Low bandwidth causes buffering [OK]

Hint: Buffering means data flow is too slow [OK]

Common Mistakes:

• Blaming compression for buffering
• Thinking CDN proximity causes buffering
• Ignoring network bandwidth limits

5. To design a scalable video streaming system handling millions of users, which combination best manages massive data efficiently?

hard

A. Use compression, CDN, and load balancers to distribute traffic

B. Store all videos on a single server with no compression

C. Send raw video files directly from origin server to users

D. Use only firewalls to control data flow

Solution

1. Step 1: Identify scalable components for massive data

   Compression reduces data size, CDN caches content near users, and load balancers distribute user requests to prevent overload.

2. Step 2: Reject inefficient designs

   Single server can't handle millions; raw files cause huge bandwidth use; firewalls control security, not data scaling.

3. Final Answer:

   Use compression, CDN, and load balancers to distribute traffic -> Option A

4. Quick Check:

   Compression + CDN + load balancers = scalable streaming [OK]

Hint: Combine compression, CDN, and load balancers for scale [OK]

Common Mistakes:

• Ignoring load balancers in scaling
• Relying on single server storage
• Confusing firewalls with data management