This video on WhatsApp system design is super informative and easy to follow. The way you broke down the concepts, along with the animations, made everything click. Really well done! ❤
@ankittiwary37122 күн бұрын
Awesome sir❤❤❤
@ankittiwary37122 күн бұрын
❤❤❤❤❤❤❤❤
@stevemiller1233 күн бұрын
Why consider upper and lower case using base 62? you only need lower case for URLs
@thecloudstories6 күн бұрын
Content delivery is excellent.
@VikasTripathi10 күн бұрын
Great video. Explaining designs in super quick time with rich information.
@tillapudisudhakar749911 күн бұрын
Thank you Suresh, This was an incredibly clear and detailed explanation! The way you broke down such a complex design and made it so easy to understand is truly commendable. Thank you for the effort you put into this!
@tillapudisudhakar749912 күн бұрын
Thank you team, fantastic work i have gone through the complete series of your videos on System Design, Your presentation & teaching is just awesome. Thank you.
@tillapudisudhakar749912 күн бұрын
Thank you so much for providing such a valuable explanation with clear visual cues-this is by far the best content I've come across!
@PrinceRajabhi16 күн бұрын
if it wok like this then what scenario for instance online sharing the current activity ONLINE or OFFLINE
@suyashgandhi868016 күн бұрын
Hitman khelega?
@sweetcodey16 күн бұрын
chal
@aneeshbose132316 күн бұрын
I think a slight modification needs to be made for Max’s request to fetch the last seen time for Emily. He needs to send his current timestamp too. If this time is the same as Emily’s last seen time stored on the server, with some tolerance for propagation delays of messages via web sockets, it should show online instead of last seen.
@ananthvishwanath774117 күн бұрын
You are great ❤
@MikeO8918 күн бұрын
Websocket is a bit overkill for a ping style system. You lock up a connection, making load balancing less efficient during peak times when a lot of users are on the app, especially during hot shard situations. Chances are its probably easier to trigger an update to the db when a common existing request comes in, like read/write message requests
@mayanksinha884118 күн бұрын
Nicely explained 👌🏻
@praneethm514Ай бұрын
Good explanation 😄
@venkatprasad6957Ай бұрын
interesting, it would be more insightful to know the redirection and how they handle the addition of new route to their domain
@sweetcodeyАй бұрын
That is a very important part of TinyURL design. You can understand that flow here at 32:12 - kzbin.info/www/bejne/eX_Mp4OlYpKZaK8 .
@HealthHacker4UАй бұрын
Helloooo please post all videos of buzzwords of system design.
@sweetcodeyАй бұрын
Thanks for reaching out @HealthHacker4U ! We are glad you are loving our content. We will soon be adding more buzzwords videos.
@wahajahmed1753Ай бұрын
Great but what about birthday paradox which actually broke md5 since checking from the database within millions of records is not gonna work
@AvinashSingh-tr5vtАй бұрын
Thank you for amazing content
@anupkaushik9370Ай бұрын
Please make a full tutorial on Message queue with flow diagram .
@sweetcodeyАй бұрын
What exactly are you interested in knowing? The inner functioning of Message Queues?
@SummiGandhiАй бұрын
Superb! Quality explanations <3
@tanishajaiswal75592 ай бұрын
Everything is so good sbout this video... the sound, the video quality, explanation, the concept.
@abhishek-942 ай бұрын
Good video. When you say FB has 30,000 servers does it mean those servers are there only to accept requests and call the data layer to get data? Or do they do some processing as well?
@sweetcodey2 ай бұрын
Good question! When we mention Facebook's 30,000+ servers, we’re referring to all the servers that handle various tasks across the platform, not just those fetching data. Yes, some servers amongst these 30,000+ will be fetch data from the data layer; while others will process user actions like 'likes'; some will run machine learning algorithms for personalized feeds etc. The idea is to explain, how much horizontal scaling could be needed depending on the number of users using our platform.
@ss-xh3hf2 ай бұрын
Great 🎉😊
@apurvkumar95052 ай бұрын
Very nicely done 💥
@adityamehta5432 ай бұрын
Great Video!! I had one doubt, in this video, first we are uploading the complete video in blob storage and then through content processor we are chunking the video and doing multiple things with it. But the main concern is that how would we be able to upload let's say a 2 hour video directly to the s3. I feel the chunking should happen in the client only and client should send chunks to upload rather than client sending complete video to content upload service which is uploading the complete video first to blob storage and then chunking it and putting it back to blob storage again. Would love to know your thoughts on this
@sweetcodey2 ай бұрын
@adityamehta543 That is a wonderful question first of all. The answer to your question is at 12:14 where we talk about Resumable URL. Server sends a Resumable URL to client which it uses to upload the content. Now, even if it is 2 hour long video it doesn't trouble us. The upload gets paused and resumed based on the internet connection. But why aren't we chunking at the client at the very first place? Well, chunking on the client can be resource-heavy, especially on low-end devices or poor networks. By chunking at the server, we simplify the client’s workload and get better control over how we process and store the video. That said, client-side chunking can be useful in some cases, especially for large uploads. It’s a trade-off depending on the use case.
@adityamehta5432 ай бұрын
@@sweetcodey Thank you so much for answering the question! This truly helps and also the video explaination is amazing. I have few more concerns also, if you can take it up-: 1) Can you also talk little bit about search functionality here, if we have to include search service, how would it interact with elastic search and will elastic search get the data from video db and then index on it and return ? Just how it will look like if you can tell over text only. 3) Uploading a video is a functional requirement , but notification is also functional requirement? Thank you so much and sorry for bombarding the comment section with questions. The video is very detailed and I am learning a lot from it.
@sweetcodey2 ай бұрын
@adityamehta543 Thanks for the appreciation! 1) Regarding the search functionality, it might be more than what’s needed here. In an interview setting, we recommend focusing on core features like upload and stream. Search is an extensive topic on its own, and we’ll dive deeper into it in future KZbin videos and courses at sweetcodey.com. 2) As for notifications, they can be a nice touch if the interviewer brings it up, though it's not essential. It wasn’t part of the original functional requirements, but we think it’s a valuable addition if time permits.
@sureshgandhi20263 ай бұрын
Succinct and crisp
@hinashekhar82563 ай бұрын
Very nice.All the best
@apurvkumar95053 ай бұрын
Awesome !!!
@apurvkumar95053 ай бұрын
Very clear yet detailed explanation, loved it !!! 👌
@sweetcodey3 ай бұрын
Glad you liked it Apurv.
@sureshgandhi20263 ай бұрын
Bring it on! Loving it
@sureshgandhi20263 ай бұрын
On point, great delivery, looking to get more in this series!
@VegitaBleEater3 ай бұрын
Love the thumbnail Rohit bhaiya
@rohitjain93813 ай бұрын
Thank you
@apurvkumar95053 ай бұрын
Great analogy, awesome channel !
@rohitjain93813 ай бұрын
Loved the explanation!
@satyendrakumarbaghel78483 ай бұрын
very well explained
@rohitjain93813 ай бұрын
Audio is soo crisp. Loved it! And also the explanation.
@rohitjain93813 ай бұрын
Loved the explanation. Simple and easy to follow.
@rohitjain93813 ай бұрын
Looked to be a difficult word but turns our sharding is just dividing the database into parts. Well explained!
@rohitjain93813 ай бұрын
Great video! Loved the highlighting and clean visuals
@rakeshgandhi13263 ай бұрын
Nice
@SHIVANJAY6193 ай бұрын
great video, to the point and succinct. looking forward to next videos in the series
@rohitjain93813 ай бұрын
Loved the fun fact and the visuals were awesome!
@devendralohar73293 ай бұрын
Great explanation and visuals
@rohitjain93813 ай бұрын
Great Video! Love the visuals and easy explanations.
@suyashgandhi86803 ай бұрын
Very well explained
@shishirchoudhary545 ай бұрын
Woaah! really liked the video , masterpiece for intuition.