Interview Bootcamp
Vote

0% completed

​

Designing Youtube or Netflix

Every case study in this chapter follows the same seven steps from System Design Interviews: A step by step guide, and builds its design from the components in the System Design Master Template. Keep both open beside you, and try each problem yourself before reading the solution.

.....

.....

.....

Like the course? Get enrolled and start learning!
H

hpyangjiayue

· 2 months ago

Storing the videos in HDFS is basically not a good practice. And there is no trade off discussing why would we choose HDFS. This system design material is too basic and not helpful!

Show 1 reply
Mohit Jayee

Mohit Jayee

· a year ago

The design diagram shown in video is missing in the writeup. I think it should be included in the write-up as well, as it makes it easier to keep it open while watching video.

Show 1 reply
Jonathan Morales

Jonathan Morales

· 2 years ago

I'm so confused why does it say to use a file storage system when an object store is so much faster and better for videos specifically in this cases where you show and store videos publicly like youtube.

Show 1 reply
Akib Ali

Akib Ali

· 2 years ago

there is nothing mentioned how view video will work, protocol, stream chunks and their orders.

Show 1 reply
C

Chris

· 4 years ago

In the "Cache" section, you say "Our service should push its content closer to the user using a large number of geographically distributed video cache servers".

Isn't this essentially what the next section, "Content Delivery Network" describes? Is there some difference between the two?

Show 1 reply
M

Mohammed Shoaib

· 4 years ago

Looking at the data size, Doesn't it make sense to store metadata as well in NoSQL. Math as follows: 230 videos per second, assume it takes 5MB to store metadata of a video. Total metadata per day = 230 * 10^5 * 5MB = 115 * 10 ^ 6 MB = 115TB. (10^5 seconds a day) At this rate, SQL DB becomes a bottleneck.

Show 1 reply
C

calvio

· 4 years ago

The system design interview is all about discussing trade-offs. How can you have a "Database Schema" section without discussing pros/cons, let alone any other alternatives?

J

Junaid Effendi

· 4 years ago

Similar Q as previous chapters. VideoID sharding would still need Consistent Hashing to avoid future redistribution.

If we go with static modulus, 100 db servers meaning, videoid % 100, means when we need more we need to reshuffle the data.

Also, why not use nosql in this case? Since they can easily scale horizontally unlike mysql which are good with vertical scaling.

Show 1 reply
J

Junaid Effendi

· 4 years ago

Load Balancing... If consistent hashing with http dynamic redirection would not work, then whats the solution?

Show 1 reply
O

ondakikamgittibunubulmakicin

· 4 years ago

Why do we use RDBMS instead of NoSQL. Same type of structures were stored in NoSQL in previous designs?

Show 2 replies

Reading Progress

0%

Vote for new content