In 2022, this interview will get a strong hire rating, but in 2024, this will get no hire unfortunately

Hey, first of all this is a great video! I have one question in the metrics section, why is the TPS calculated based on how many users? The transactions should include no of users and their activities like uploading a photos, generating newsfeed and following other account, right?

this is really great stuff!

thanks Mark!

One of the worst explanations for an SD problem. No context on the approaches. Straight away dived into DLL, I mean WHY? Worst video from this channel. Complicated it without any reason.

That's really useful. Thank you!

Thanks Jordan!

How this note board is call guys?

How did he get to the conclusion of using linked list? why not using heaps to keep the max and min prices?

This is not bad but barely passable for L5 and certainly not an L6+ material. There are a lot of holes. Redis Pub/Sub for instance is very fragile part of the design. Also it would be very hard to get the people that a user follows quickly. There were bunch of hand wavy stuff, if we're partitioning by Tweet ID, why does it matter that the Tweet ID is ordered? If we're partitioning by the user and then by the tweet ID then each tweet will still go to a different server. What's the purpose of it? I mean there are some big holes. We did the capacity planning and what purpose did it serve? What did it help with? Just waste of time? The more I think about it, L5 hire is hard actually maybe L4.

Get system design interview coaching and get the offer: igotanoffer.com/en/interview-coaching/type/system-design-interview

Fake accent😂😂😂

accent f***** up

She’s a baller, mucho gracias!

When Spotify started, their main USP was to load the song within few milliseconds and that they did with the help of p2p network which they abandoned a few years later to use more traditional approach like Mike explained.

not experienced senior

question : if requirement is to show historical data, how would you modify?

Good point: Listen to the interviewer. He told me that he has more questions to ask me and that I need to finish the system design and explain the call flow in 5 minutes , which I did. We covered more questions and answers. It was a friendly way testing someone’s depth and breadth knowledge and experience in a short time. Good luck every one.

is really funy this type of questions "design tiktok", "design youtube"... "design x..", for a senior /mid role, dude , if a person could design those companies, he should be applying for an investment from sequoia or Y Combinator

Thank you for sharing this amazing knowledge!

Amazing !

I work on Spotify and I can guarantee that you read this message and you felt excited, but I was lying.

Interesting stuff and the technical choices were on point! One thing i would Improve though is defining and slicing the requirements into bounded context related services. For example we could have defined the contexts: User, Video and Suggestor. Each would be represented by its own building block initially allowing to scale or break one up more, if needed. The suggestor then would have relations to User and Video and would (based on ML for example) generate video suggestions for different parts of the app. Video would be responsible for CRUDs on content and handle metadata and their blobs. The user would utlise this one when loading videos based on the suggestor result for example or the upload etc. The User context would handle user metadata, relations like friendship and possibly views. For each we can find specific solutions for their storage, scaling, concurrency etc. needs.

IGotAnOffer: Engineering has some excellent content, especially for the technical interviews. Thanks guys!

what tool are they using for design?

Thank so much great advice for salary negotiations

10 Mins. on calculation. like seriously!!!?? Moreover explanation on why Sql, is very incomplete and vague. Dang!! No Hire

Mark doing a perfect interview. Tom: "nice attempt" :))

What is the name of this drawing/diagramming tool which is used by Karthik?

I'm having an interview at swiggy and i went through out several of youtube videos to understand that how to design an system at high level or low level but this is what I'm searching for , which made me confident to make answer in the low level design interview that how things work and function. Thank you so much

I'm having trouble seeing the difference in data size between video metadata and users. One billion users, each with 200 friends, that's 200 billion rows of data. Is that not similar in size to 10 Billion per year video metadata rows?

Can we still use a CDN if there is a contract/mandate that only auth'ed users can get a song (/song chuck)? its not too clear if the CDN will blindly return to any valid URL regardless of HTTP headers (ie, auth token)

Is it not Imp to be correct on these calculations I think the calculations around BW were in correct instead of 10% it has been 1% i think that needs to be called out. Also I think assumption needs to be a little more realistic the assumption of 200Kb for photo was absurd.

One of the very complex systems which could've been simplified.

Thank you so much Karthik. Previously, even though I knew the technical concepts, I had absolutely no idea how to present them. Because of that, I think I missed a few good opportunities in the past. This video helped me a lot to organize my 40-minute presentation very clearly along with a lot of technical knowledge.

Is there any book or tutorial best for learning system design

Can I answer that It’s impossible to build 1 billion architecture from scratch? It’s a process?

This is some of the best behavioral interview specific EM content and perspective I've come across. Hidden gem of a video -- thank you for sharing it.

Yeah lol, could you get Mark to redo the system designs for Uber, no offense but Mark is way better in explaining and going into detail about the design, detailing the speficing databases needed to be used, what languages are need to script the app, as well as server side langugages needed to handle incoming and outgoing requests from the client.

this is great but not yet tackle the most important part of an app like spotify is how u deal with real time streaming data. either u download the whole song into the phone before it play or u do it real time. the real problem here is in the matter of 0.3s after the user click, song must be played.

Nice Video, thanks guys. As I am seeing, Mark is having eye contact to us und the sound is very nice too, I wonder if you could share, what the setup is on Marks side!

Useful video but IMO the guy spent way too much time on metrics. The interviewer should have moved him forward to focus on the architecture.

Thanks for the video. But it wasn't really focusing on the essential parts. 30 mins passed and then he starts doing high level design... In a real world interview, I think this was a reject.

The interviewer is weak sauce, and should not be interviewing.

Maybe (most probably) I'm stupid - but how do a connection-based protocol and caching play together?

It all sounds a bit naive. Drilling part supposed to be based on follow up questions going as deep as possible reaching candidates knowledge limit. Please don’t expect anything like this for a senior role.

why 20 followers not 200 followers?

you dont need song url..... it is better if its auto generated based on the id.....

why media service is interacting with CDN?

19:54 yes we did put a number there :)