@aytonjim6225
babe wake up, a new hello interview system design video just dropped
@alexanderfournier7292
The diagram outlining when to choose simple polling vs SSE vs Websocket vs WebRTC is fantastic.
@nikoskoufos2588
I just want you to know I know this is geared for those interviewing at companies but I have been using your content to just become a better engineer in general! I've gotten a callout from my manager who has noticed a considerable increase in quality in my contributions to system design at our company! Thanks so much and keep up the good work!
@mahim_mahbub
Hey, I wanted to express my heartfelt gratitude. I followed the mock interviews and deep dives from this channel, as well as the resources from your website during my preparation. I strongly believe that it helped me a lot for my system design round at Amazon. I got the offer as an SDE 2 at Amazon a few months back, and my first day was a couple of weeks ago. Thanks so much for the awesome content !
@charan775
thanks to your videos I got offer from Uber.. your approach to problems was very helpful
@adeeshacharya7520
There are lot of youtube videos out there, where they teach the same thing, But after watching your video, I just can't watch others. This is just perfect for me atleast. Please keep posting such videos
@nelsonkatale808
I love how he breaks down the things in such a way that a beginner can easily get it. ❤
@rahulsbhatt
I have a lot of new concepts just by watching this single video! The structured framework also helped in thinking in the right direction. Thank you for posting this sir!
@abhilash8973
i forgot it's 1:23 AM here when i completed this video. Loved it!
@katearcher8881
You could use DynamoDB's TTL attribute to automatically delete old messages. S3 also supports removal policy, so it can take care of old objects automagically. Big thanks for the video!
@IYI_WOLF_IYI
I had to re-watch parts of this video multiple times and I was wondering why. I think it might be because Stephan tends to be a bit "fancier" and varied with his wording, which makes it harder to follow when you're less familiar with these topics and learning. Also I think Evan tends to use fewer run-on sentences and has clear pauses between points, whereas Stephan tends to "ramble" a bit more, even when correcting an error mid-sentence. I think a good example was around 29:40, which based on the little graph YouTube provides on the "most rewatched" parts of the video, it seems like that was the section people rewatched the most times likely because it was confusing for them too... Maybe it might help to write more notes on the page for the chunks of the video where its purely just verbal explanation? Don't get me wrong, I love the content and I've learned so much through it, but it might be worth matching Evan's style and pace or analyzing what it is that makes him so clear to understand. Thank you for making the videos Stephan and Evan!
@rohit-ld6fc
System design is easy, Alex Xu by made it super hard. He put things which no one can do without preparing for months. And everyone started believing ohh yes 'this is what I need to study to crack SD interviews'
@mohammedshahulpm4750
Wow, so great! I have been going from video to video to understand system design of a chat system and find the best queue suitable for this. I finally found this video-- thanks a lot, man! You are a gem
@dishankchauhan8679
Hats off to you and to the entire team for making these system design videos very interesting and super easy to understand 🙌 🙌
@3rd_iimpact
Perfect timing. I was in the middle of reading the article until this video popped up. Thank you!
@rushio8673
I would like to thank you both for posting very meaningful content, I have an interview with Meta in a few days, fingers crossed ! I also would like to point out that this has made me learn a lot about architecture in general as well as I've started liking my job as a software engineer a lot more by learning from people like you ! Thank you once again.
@eastsideGK
Been waiting for this one!
@Procrasterate
Really enjoying this series of videos, strange to me though that you are choosing DynamoDB but then not utilizing the partition-centric nature of DynamoDB as part of the data design. There was no mention of how one could use Dynamo's partition and sort keys for the kinds of queries you need vs. normalizing everything across multiple tables using foreign keys (which is commonly considered a DynamoDB anti-pattern.) Also, no mention of how at these massive scales one would also provision these systems globally across multiple regions (meaning multiple DynamoDB deployments, multiple Redis clusters etc), and functionally allow for chats between people across the globe (who are not connecting to the same region) and also still need to isolate for datacenter-wide failures (ie. no cross regional dependencies) AND we have to build a failover solution for all that. Fault-domain isolation, resiliency, and recovery from failure in these massive systems with global deployments is I think an important part of every design discussion at a senior level, but I rarely hear anyone talk about it. Finally, I assume we're defaulting to IPV6 across our system due to connection limit issues with IPV4 but it was not mentioned that I recall, maybe that's a given these days?
@danyald4880
Always waiting for your videos. Top quality.
@hello_interview