Видео

Even though I’m morbidly obese Imma try to stay away from Ozempic or drugs like it. I don’t wanna get dependent on yet another drug just to be normal.

This guy is definitely an experienced engineer, but he didn’t prepare for this kind of interview very well, maybe he is a little bit nervous during the interview. He is trying to say a lot terms like s3 to make him sounds professional but lost many details on how to design the solution from scratch like handling big files. This is a question about designing Dropbox, not use case of s3. The performance would be rejected for any senior positions.

How would guarantee strong consistency here ?

I don't understand how can we use round robin and also use websocket? Shouldn't the user directed to the same server because this server have this connection open there ?

Why did he choose cassandra not any sql db? His explanation is not clear

Thoroughly enjoyed this interview

Hey I know this guy. I haven't had much experience with having to do System Design interview questions as a Data Engineer. However, I still think that it can be highly beneficial to start prepping now just in case. Not every DE role requires System & API Design questions. My challenge may also be s.t. I don't have any real-world experience building APIs so I am unsure if that would diminish my ability to land role despite being able to pass the API design round.

Thanks for the effort on this channel! But I really didn't like either the design or the scheduling of the interviewee. His priorities of discussion was terrible and focused a lot on not-very fun and important parts of the design instead of timeline generation and celebrity issues for a system with 1B users!. Was not clear why we have an extra service right before the Kafka queue ( why not just directly go from LB to Kafka) and then the uploader reads from Kafka and uploads/updates the storages and many more other issues for a design like that.

This is great - it would be great if you can also have some Principal Mobile Engineers come on your channel and do a Mobile App Design/Architecture interview.

Mark mentioned about pulling meta data and then when the request for song comes in we again need to go to the RDS DB and then hit the MP3 link in S3. Can we not retrieve the Mp3 link when searching for the songs and directly hit the S3 link when we want to play the song ? Will this help ? Please suggest.

why not use something like consistent hashing for a user layer which will give it a scaling capability ?

how important are the data calculations for this kind of interview?

For 100 million users, shoul it not be 1.5 exabytes?

What this interview really shows is that you don't really need to know every detail of the future solution(spotify i much more complex than this), but those solutions that you choose to invent - you should be capable of explaining why they are needed in the most understandable way.

What is the app you are using to write/draw?

As an employer: do not use any of these videos as an expectation for how an interview will go. It won't look anything like this, and if you prepare for something like this, it will not go well

Great video. The way he approaches depth shows that he is very strong

I believe the math is incorrect you must take 100M users * 15 GB to get to the total which is 1,500 PB

Wild that he didn't think about bandwidth. This is the make or break number for any streaming service

29:20 I like how he handles the data mining and parallel processing more easily by sharding, and the billing service is sharded too to match it , so each worker can split the shards

Did we actually need a message distributor? Why not add the messge to the recipient's unread messages the moment it gets posted by the sender?

Unconventional. No feature scoping, no API design. No QPS / bandwidth / storage estimation. Diagramming too late. No mention of multiple devices per user. Not mentioning data structures. Great, confident speaker though.

There is no database on the high-level diagram. Then, in drill-down, Alex jumps to designing DB schema.

Get billion millionaire cusytomerd. Dont guess the capacity. That amazon babies talk. Did you guess the capacity??

Such a great video, thank you!

Where can I find Mark's resume? Does he have a LinkedIN account?

He is just genius!! The way he is explaining is REMARKABLE!

Too much time into math and numbers??

Thank you for the good system design interview. Also was wandering why @crushingtecheducation has no content?

This interview is full of mistakes by design, correct? Just to make us start thinking.

thanks, was really usefull

5TB/day i.e. 5*365 = 1825TB = 1.8 PB/day correction required here

Did you guess the capacity? There are more machines than you can count. Now design

Get 1-to-1 coaching and ace your tech interviews: igotanoffer.com/en/interview-coaching/type/tech-interview

CDN on spotify? for real? I dont think this works like that, CDN doesnt directly read from blob storages either. CDN is for loading the 1st page of your website quickly, not stream a 5mb song directly. Way off I feel on this point. also, where is the auth layer? security layer? etc this is very very high level.

Great video!!!

Dima is an architect at Miro. Of course, his depth of knowledge and expertise is not represented in a typical system design interview conducted by average engineers. I appreciate having the opportunity to watch his interview. This is another level.

Great, actionable and contemporary insights & resume tactics, Cody!

Excellent resume video live now: ruclips.net/video/YCQyIy-1Tn0/видео.html

Get 1-to-1 resume coaching from ex-FAANG recruiters: igotanoffer.com/en/resume-service/type/tech

I was asked once a question to design a system. My interviewers liked the question from my side. I asked them the following. Am I leading this project or, am I just an expert in a certain part of it? They liked it because I asked if I should focus on general architecture or leave more space for a particular component. Which also has to be properly designed. Anyhow, this interview was fantastic. Thank you.

I would have loved to see how albums, playlist, recommendations and song radio world be stored and served.

23:00 avoid the db lookup for url. In the service you can generate the audio url from the songid you have in the metadata. You can keep the dbs truly uncoupled. Maybe he comes to that part but I've paused the video and commenting right now.

Is that bit about partitions in S3 accurate? S3 uses a key-based structure where each object is stored with a unique key. The key can include slashes ("/") to create a hierarchy, effectively mimicking a folder structure but there aren't any actual folders in S3; it's all based on the keys you assign to your objects. So, what does he mean by splitting into more folders when they become too large?

I think adding the Loging Auth on the client side is not recommended for security reasons. One of the points which my Interviewer didn't seem to be happy about....and since that was for the security team I think that cost me losing the offer

Would have been nice to compare this approach to an Append-only-log structure like Kafka as a store - I suspect that's where we would have ended up if group messages were part of the design. I think not handling groups was a miss here. I would expect a senior/staff/principle candidate be able to talk about the added scaling needs of group chats.

This candidate has real life experience and it shows in the interview. He starts out simple and build on top of it. I love it.

I find it unnecessary that these interviews spend time on calculating the amount of data that will be stored.

"10. Use the drawing tool efficiently" - this is present in description, but missing in Chapters list