Why not use a No SQL based DB while uploading videos? We wouldn't have to do the extraction in that case right? We can simply just work with the meta data DB in JSON format.
Great video. I am new to system design, just watching for fun. I was not satisfied with the search deep dive, I don’t know how it’s actually done, but I feel this would not be a convenient way, please correct me if I am wrong. And apart from that I also am unsure why he replicated the video to another CDN, how would that help 37:13 ? Could anyone please answer my questions?
What he is talking is about inverted index, which is a popular concept used by lot of companies to handle search from a huge dataset kind of use-cases. Since you are new to system design, I am sure once you go through Elastic search and inverted indexes to understand the search related stuff, you will better relate to what he explained. Cheers! CDNs are networks of distributed servers strategically positioned across various geographical locations. They are designed to deliver content to users more efficiently and reliably by reducing latency and ensuring high availability. Again it is widely used in the industry for improving performance of static content delivery like videos, photos, etc. It is highly optimised for that.
this is a good sample interview how to do what you seen, the initial theory the assumption the drawing the database choice the explanations of the choices you made and the vague and BS answers you give should not be done at all. He is the definition of question evader and bullshitter, or he simply is not good at explaining what is in his head or the interviewer is not correcting him since mostly he was quiet listening.
Ya when he was asked why he was using that database he just repeated question like 3 times saying it's a Blob database so that's why I'm using it because it's a Blob database. So he kept restating what but not why
I don’t really understand the point of going into such detail on the calculation aside from going “wow that’s a big number” they never really use these in any meaningful way. I often prefer to do some calculations when it’s important and actually impacts my design.
its done for demonstration purpose that you are equipped with the skills of reasoning and thinking ahead of the design number-wise. Also it shows your understanding of the edge cases, I could point many miss conceptions of his numbers and assumptions, but usually those are not contested because the point of the interview is not to be 100% correct on this segment. The point is to demonstrate the capability to work on a design with a team.
Not exactly. I am not sure if you have faced top tech (FAANG) interview for senior+ levels. I have faced interviews for top tech companies (even cracked a few). As you move up seniority level, deep dives and details are what sail you through. By details, it can be in any direction that interviewer suggest like regarding a particular implementation, how a certain process actually works given the components that you propose in the design and any other flow deep dive that interviewer in interested in. Some times the design discussion is for a particular API implementation - on how the API is implemented and how you would scale it. For top tech and specially for system design, there is no clear demarcation that it should be high level only and not low level. It is purely driven by the conversation and with seniority the level of deep dives you go into is super super important, else you would be low levelled by the company. Speaking from personal experience where I received feedback that I did not cover enough details in the design ands did not go into deep dives.
@@PeopleTeam-vi5cw True. 100%. Faced the same. There is no rule that low level is not part of System Design. For senior levels, low level and specifics are expected. Only touching the surface and generic/common design won't sail through! 👍
Popular adaptive streaming technologies include Dynamic Adaptive Streaming over HTTP (DASH), HTTP Live Streaming (HLS), and Microsoft Smooth Streaming. th-cam.com/video/hqa2sfoGRlI/w-d-xo.html
Get 1-on-1 coaching to ace your system design interview: igotanoffer.com/en/interview-coaching/type/system-design-interview?TH-cam&
i believe using an elastic search on the metadata db, would be much more helpful for searching /fuzzy searching.
Thank you. Awesome interview
Why not use a No SQL based DB while uploading videos? We wouldn't have to do the extraction in that case right? We can simply just work with the meta data DB in JSON format.
thank you good design
Great video. I am new to system design, just watching for fun. I was not satisfied with the search deep dive, I don’t know how it’s actually done, but I feel this would not be a convenient way, please correct me if I am wrong. And apart from that I also am unsure why he replicated the video to another CDN, how would that help 37:13 ? Could anyone please answer my questions?
What he is talking is about inverted index, which is a popular concept used by lot of companies to handle search from a huge dataset kind of use-cases. Since you are new to system design, I am sure once you go through Elastic search and inverted indexes to understand the search related stuff, you will better relate to what he explained. Cheers!
CDNs are networks of distributed servers strategically positioned across various geographical locations. They are designed to deliver content to users more efficiently and reliably by reducing latency and ensuring high availability. Again it is widely used in the industry for improving performance of static content delivery like videos, photos, etc. It is highly optimised for that.
this is a good sample interview how to do what you seen,
the initial theory the assumption the drawing the database choice the explanations of the choices you made and the vague and BS answers you give should not be done at all.
He is the definition of question evader and bullshitter, or he simply is not good at explaining what is in his head or the interviewer is not correcting him since mostly he was quiet listening.
10 Mins. on calculation. like seriously!!!??
Moreover explanation on why Sql, is very incomplete and vague.
Dang!! No Hire
Ya when he was asked why he was using that database he just repeated question like 3 times saying it's a Blob database so that's why I'm using it because it's a Blob database. So he kept restating what but not why
I don’t really understand the point of going into such detail on the calculation aside from going “wow that’s a big number”
they never really use these in any meaningful way.
I often prefer to do some calculations when it’s important and actually impacts my design.
its done for demonstration purpose that you are equipped with the skills of reasoning and thinking ahead of the design number-wise. Also it shows your understanding of the edge cases, I could point many miss conceptions of his numbers and assumptions, but usually those are not contested because the point of the interview is not to be 100% correct on this segment. The point is to demonstrate the capability to work on a design with a team.
He kinda got stuck between system design and low level design. You probably don't need to go to a much deeper detail in system design
Not exactly. I am not sure if you have faced top tech (FAANG) interview for senior+ levels. I have faced interviews for top tech companies (even cracked a few). As you move up seniority level, deep dives and details are what sail you through. By details, it can be in any direction that interviewer suggest like regarding a particular implementation, how a certain process actually works given the components that you propose in the design and any other flow deep dive that interviewer in interested in. Some times the design discussion is for a particular API implementation - on how the API is implemented and how you would scale it. For top tech and specially for system design, there is no clear demarcation that it should be high level only and not low level. It is purely driven by the conversation and with seniority the level of deep dives you go into is super super important, else you would be low levelled by the company. Speaking from personal experience where I received feedback that I did not cover enough details in the design ands did not go into deep dives.
@@PeopleTeam-vi5cw True. 100%. Faced the same. There is no rule that low level is not part of System Design. For senior levels, low level and specifics are expected. Only touching the surface and generic/common design won't sail through! 👍
Too much time into math and numbers??
Yep. And all in vain. He forgot about trans-coding and storing one video in multiple formats. 100MB / vid is way too humble of an estimate.
@@MinekEzQM: Yup he should have multiplied the total size by 10. Roughly 3 formats with 3 times replication.
Agree. numbers part can be an improvement in this design and that's a learning from the video.
@@sathyans3852 YES , VIDEO IS INFORMATIVE
HI
Popular adaptive streaming technologies include Dynamic Adaptive Streaming over HTTP (DASH), HTTP Live Streaming (HLS), and Microsoft Smooth Streaming.
th-cam.com/video/hqa2sfoGRlI/w-d-xo.html