Video upload and processing pipeline in HLD - System Design Guide

Problem Statement

Uploading and processing videos directly on a single server causes slow response times and frequent failures under high load. Large video files can overwhelm storage and CPU resources, leading to poor user experience and system crashes.

Solution

The system breaks video upload and processing into separate stages using asynchronous queues. Users upload videos to a scalable storage service, then processing tasks like transcoding and thumbnail generation run independently in worker services. This decouples upload from processing, enabling smooth scaling and fault tolerance.

Architecture

User

→Upload Server

↓

↓

Video Worker

(Processing)

↓

Metadata DB

This diagram shows the flow from user video upload through upload server to storage, then asynchronous processing via message queue and worker services, ending with metadata storage and content delivery.

Trade-offs

✓ Pros

→

Decouples upload and processing to improve system responsiveness and reliability.

→

Enables horizontal scaling of upload servers and processing workers independently.

→

Allows asynchronous retries and failure handling without blocking user uploads.

→

Supports large video files by offloading storage to scalable services.

✗ Cons

→

Increased system complexity due to multiple components and asynchronous flows.

→

Potential delays between upload completion and video availability due to processing time.

→

Requires careful design of message queue and worker scaling to avoid bottlenecks.

Use when handling large video files with high upload volume and complex processing needs, typically above hundreds of uploads per minute.

Avoid if video uploads are rare or processing is minimal, as the added infrastructure complexity may not justify benefits.

Real World Examples

YouTube

Separates video upload from transcoding and thumbnail generation to handle millions of uploads daily without blocking users.

Netflix

Uses asynchronous pipelines to transcode and package videos for multiple devices after upload to storage.

TikTok

Processes uploaded videos asynchronously to apply filters, compress, and prepare for fast delivery.

Alternatives

Synchronous processing

Processes video immediately during upload request, blocking user until completion.

Use when: Use only for very small videos or low upload volume where immediate availability is critical.

Edge processing

Processes videos closer to user devices or edge servers to reduce latency.

Use when: Use when low latency is critical and edge infrastructure is available.

Summary

Video upload and processing pipelines separate upload from processing to improve scalability and reliability.

Asynchronous queues and worker services handle heavy processing without blocking user uploads.

This design supports large files and high upload volumes while enabling fault tolerance and smooth scaling.

Practice

1. Which component in a video upload and processing pipeline is primarily responsible for converting raw uploaded videos into multiple formats suitable for playback?

easy

A. Content delivery network (CDN)

B. Video processing service

C. Metadata database

D. Upload service

Solution

1. Step 1: Identify the role of each component

   The upload service handles receiving videos, the metadata database stores info, and CDN delivers content. The processing service converts videos.

2. Step 2: Match the function to the question

   Converting raw videos into multiple formats is done by the video processing service to ensure compatibility.

3. Final Answer:

   Video processing service -> Option B

4. Quick Check:

   Conversion = Video processing service [OK]

Hint: Processing means converting video formats [OK]

Common Mistakes:

• Confusing upload service with processing
• Thinking CDN does video conversion
• Assuming metadata database handles video files

2. Which of the following is the correct sequence of steps in a typical video upload and processing pipeline?

easy

A. Storage -> Upload service -> Video processing -> Metadata update

B. Video processing -> Upload service -> Metadata update -> Storage

C. Metadata update -> Upload service -> Storage -> Video processing

D. Upload service -> Video processing -> Storage -> Metadata update

Solution

1. Step 1: Understand the logical flow

   Users first upload videos, then videos are processed, stored, and metadata is updated last.

2. Step 2: Match the sequence to options

   Upload service -> Video processing -> Storage -> Metadata update correctly shows upload first, then processing, storage, and metadata update.

3. Final Answer:

   Upload service -> Video processing -> Storage -> Metadata update -> Option D

4. Quick Check:

   Upload first, then process, store, update metadata [OK]

Hint: Upload happens before processing and storage [OK]

Common Mistakes:

• Starting with processing before upload
• Updating metadata before storage
• Mixing storage and upload order

3. Consider a video upload pipeline where the upload service places video metadata into a queue for processing. If the processing service crashes and stops consuming messages, what will happen to the queue and user experience?

medium

A. Upload service will reject new uploads immediately

B. Queue will empty quickly; users get instant processing

C. Queue will fill up, causing delays; users see slow processing

D. Metadata database will automatically process videos

Solution

1. Step 1: Understand queue behavior when consumer stops

   If the processing service crashes, it stops consuming messages, so the queue fills up with unprocessed metadata.

2. Step 2: Impact on user experience

   Since processing is delayed, users experience slow video availability or processing delays.

3. Final Answer:

   Queue will fill up, causing delays; users see slow processing -> Option C

4. Quick Check:

   Processing down -> queue fills -> delays [OK]

Hint: No consumer means queue backs up [OK]

Common Mistakes:

• Assuming queue empties without consumer
• Thinking upload service rejects uploads immediately
• Believing metadata DB processes videos automatically

4. In a video processing pipeline, a developer notices that some videos fail to process and the system does not retry them. Which change will fix this issue?

medium

A. Implement a retry mechanism in the processing service for failed jobs

B. Remove the queue to speed up processing

C. Store videos only after processing completes

D. Disable metadata updates to avoid conflicts

Solution

1. Step 1: Identify cause of failure handling

   Failures without retries mean the system lacks a retry mechanism for failed processing jobs.

2. Step 2: Choose fix to handle failures

   Adding retries ensures failed jobs are re-attempted, improving reliability.

3. Final Answer:

   Implement a retry mechanism in the processing service for failed jobs -> Option A

4. Quick Check:

   Retries fix failed processing [OK]

Hint: Retries fix failed processing jobs [OK]

Common Mistakes:

• Removing queue breaks asynchronous design
• Storing before processing causes errors
• Disabling metadata updates unrelated to retries

5. You need to design a scalable video upload and processing pipeline that supports millions of daily uploads with minimal user wait time. Which architectural choice best supports this goal?

hard

A. Use asynchronous upload service with message queues and distributed processing workers

B. Process videos synchronously during upload to ensure immediate availability

C. Store all videos on a single server to simplify management

D. Update metadata only after manual verification to ensure accuracy

Solution

1. Step 1: Analyze scalability and user wait time needs

   Millions of uploads require asynchronous handling and distributed processing to avoid bottlenecks and reduce wait time.

2. Step 2: Evaluate architectural options

   Asynchronous upload with queues and distributed workers allows parallel processing and smooth scaling.

3. Final Answer:

   Use asynchronous upload service with message queues and distributed processing workers -> Option A

4. Quick Check:

   Asynchronous + distributed = scalable and fast [OK]

Hint: Async + queues + distributed workers scale best [OK]

Common Mistakes:

• Synchronous processing causes delays
• Single server storage limits scalability
• Manual metadata delays pipeline