@hello_interview

Hey everyone! Thanks for being part of our growing system design community 🙌

After countless requests for deeper content, we launched Hello Interview Premium https://hellointerview.com/premium/. We'll keep pumping out free videos and content on the site, but for those looking to go deeper, Premium comes with
✓ Deep dives into core technologies and concepts
✓ Guided Practice: Work through real interview problems with instant feedback
✓ Breakdowns of the most common system design questions
✓ Fresh insights from recent candidates' actual interviews including what questions they were asked.

We're constantly adding new content based on your feedback, so keep it coming! 

https://hellointerview.com/premium/

@tabeebyeamin9986

I just finished my E4 onsite for Meta. No idea exactly if I passed the system design interview yet but I felt confident the whole time. It was thanks to your content and your mock interview services. I studied your videos and articles over and over until I could identify patterns. Every time the interviewer asked me something about a component or why I choose to use or do X it felt easy and I could answer it.

Even if I don’t pass I’m so happy with how far I’ve gotten in learning system design (and the system design interview specifically) from almost 0! Thank you so much for all you do. I hope that I will be able to use your content to pass senior+ interviews in the future!

EDIT: GOT THE OFFER!

@TimothyZhou0

The image of a comments service screaming out into the ether is somehow very funny. Liked and subscribed :)

@pankitthapar

Hi, thanks for starting this discussion—it's a really interesting one!

I debated between Kafka and Redis for broadcasting comments to users. While Kafka's consumer model is heavy and not ideal for quick changes, Redis has memory limitations if it needs to store messages for the last few hours.

Ultimately, I chose Kafka because of its durability and the ability to store messages without memory constraints. I acknowledge the overhead of consumer rebalancing, which can cause delays when a new consumer joins. However, once a consumer is established, performance is stable.

To minimize this overhead, we aim to maintain stickiness between the Real-time Messaging Service and its Kafka partition, ensuring smoother performance when new consumers are added. 

Looking forward to hearing from Hello interview

@siddharthchaudhary2183

Great first video for the year! I was waiting for this for a while.

@VirajChokhany

You're a King dude! I look forward to your system design videos. They are literally so amazing. I never have a track of time while watching your videos, its sooooo goood!!

@billbach21

Thank you so much for your videos, I'm a huge fan! 💙A small ask. Could you add smaller sections to your videos? I think it would be great to see all the great questions and topics you discuss in the sections so we can return to them and refresh our memory. For example, instead of having a huge section "Deep Dives", split it up to smaller chunks with specific topics. Again, thanks a lot for making this content! 🙏

@phelpo95

Hey, great video, really well done. 

One thing which I didn't see you mention, and maybe it's a good opportunity to talk about this in another video is that in your pub/sub solution you've introduced a potential dual-write problem, writing both to your db and event bus in a single process. 

This is definitely something I'd dig into for senior / staff+ level engineers, whether they are aware of this issue, patterns to avoid, and actually a trade off against the central dispatcher architecture.

@calvincruzada1016

We are so back

@Winistein

Perfectly explained between the choice of technologies and its advantages and disadvantages. Appreciate it a lot!

@mannishkarki

First of all let me give a huge shout out to you guys, these contents are awesome and top notch, I have been listening to these videos while I'm commuting to and from my work. I can generally follow everything you say except when you refer diagram and use words like this or that, so I just wonder if that's something you could try to incorporate in your talks. Again, this is me being super selfish and wishing for everything, but crossed my mind with huge aspect for not exactly a podcast but something people like me could connect to.

@anuragtiwari3032

Way to go. Couldn't have had a better start to the year 🎉

@chengzhihu1742

It's super helpful to read the material on the website as well as seeing this well explained video! Kudos!

@19pend

Have my FAANG interview coming up very soon. I got premium on the website (very worth it btw!) but I also find these videos very helpful. Thanks for them!

@Anj2409

Thanks for the great video. The framework has been really useful and I am incorporating the same Excalidraw boxes in my prep to stay organized. Love love the Guided practice on the website

@alihussainladiwala5929

The best content for System Design!

@alibaba888

54:52 - 54:54 i love the positivity and enthusiasim 😂😭

@Igloo683

nit: In 48:23 should it be Kafka topics and Redis channels instead of the other way round?

@user-kb5vl8hj4e

Really enjoy the content! Just have one question for the redis pub/sub. In the previous video design messenger we went with the redis pub/sub approach, and for each user we sub to a topic, that’s also a large number of topics I suppose. But in this video reason we don’t do it for video ids, but rather do it on a courser granularity. Is this because there are way more videos live streaming than live user in chat services?

@plankton383

I just found your channel. This is beautiful content. Thank you! ❤