Home
Courses
System Design

Evaluation of YouTube's Design

Evaluate the YouTube System Design by confirming compliance with requirements like low latency and high availability. Justify key architectural trade-offs, such as choosing between eventual consistency and specific storage technologies. Learn how solutions like Vitess address massive future scaling challenges.

We'll cover the following...

Requirements compliance

The proposed design must fulfill three core requirements: low latency, availability, and reliability.

  1. Low latency/Smooth streaming: We achieve this through:

    1. ISP-level caching to store frequently viewed content.

    2. Optimized storage systems (e.g., Bigtable for thumbnails, blob storage for videos).

    3. Distributed caching at multiple layers.

    4. Content delivery networks (CDNs) to serve videos from memory near the end user.

  2. Scalability: Web and application servers scale horizontally. However, MySQL has scaling limits that require restructuring, such as sharding, as the system grows.

  3. Availability: We replicate data across servers and data centers to prevent single points of failure. Local and global load balancers reroute traffic during power or network outages.

  4. Reliability: Data partitioning isolates failures, so the unavailability of one dataset does not affect others. We use the heartbeatThe heartbeat protocol is a way of identifying failures in distributed systems. Using this protocol, every node in a cluster periodically reports its health to a monitoring service. protocol to monitor server health and a variantMirrokni, Vahab, Mikkel Thorup, and Morteza Zadimoghaddam. “Consistent hashing with bounded loads.” Proceedings of the Twenty-Ninth Annual ACM-SIAM Symposium on Discrete Algorithms. Society for Industrial and Applied Mathematics, 2018. of consistent hashing to manage node additions and removals seamlessly.