How Web Sockets work | System Design Interview Basics

In this video I explain basics of Web Sockets, and compare it with Polling and HTTP Long Polling, which you must know for system design interview.
/ bytemonk
• System Design Intervie...
• System Design Questions
• LLM
• Machine Learning Basics
• Microservices
• Emerging Tech
AWS Certification:
AWS Certified Cloud Practioner: • How to Pass AWS Certif...
AWS Certified Solution Architect Associate: • How to Pass AWS Certif...
AWS Certified Solution Architect Professional: • How to Pass AWS Certif...

[@ByteMonk]

Part-2: Web Scokets Deep Dive kzbin.info/www/bejne/fWHClmNoecl7bas

[@kyleh1623]

Really appreciated how you explained web sockets in comparison with HTTP Requests, making the exact point of utilizing web sockets stand out. That really helped me understand much better🙌

[@ByteMonk]

Thanks for taking the time to comment on the video. Soon I will be publishing an advance tutorial on Web Sockets, so stay tuned :)

[@distortedjams]

Really appreciate the video. The animations made it so much easier to follow along and I completely understood it with a single watch. Keep up the great work.

[@AshootoshBhardwaj]

Great Video! For the impatient ones, jump directly to 03:20 to know about websockets!

[@oleksandrsova4803]

But you haven't explained *how* it works. Not even a bit. Like what is behind those well-known WS interfaces? What is in the TCP package? Is it any special for WS? Do we need a URL to establish a connection? How to distinguish one connection from another one? Is there a notion of a cookie? How does the session work in the context of WS-based service? How does load balancing work with WS connections? What is the usual limit on the number of WS connections? Is it a number of opened file descriptors? What it depends on?

[@ByteMonk]

Thanks for the feedback with specific examples. While these are good question, this video was made for System Design Interviews. To our knowledge, this level of detailing on web-sockets is not required in any of the Tier1/Tier2 Tech companies from System Design perspective, unless one is applying for a speciality position. Based on my market research, I may plan to deep dive on websockets in future. Thanks again!

[@narebinhaa]

He means that the title of this videos should not be "How websocket work". It should be "What is websocket".

[@Tyrone-Ward]

I like how 90% of this video has NOTHING to do with Websockets 😂

[@bluesquare23]

I could listen to you say "full duplex asynchronous messaging" all day.

[@fatbubble123]

It is so easy to study for my system design interviews when I have so much quality youtube to click through, quite lazily I might add. Thanks for the amazing videos!

[@betterwithrum]

As others have said, this is some of the best content on KZbin. Could you do a complete course on K8S? I’d happily pay for it

[@RadenVijaya]

I learnt this is computer communication lecture many years ago. Glad to have a refresher now!

[@sahaneakanayaka3394]

Crystal clear explanation

[@chaudang1279]

Hi there. Thank you for sharing such a well-presented and easy to understand explanation. Can I ask for your permission to remake this video and translate it into Vietnamese to share with my audiences on KZbin? Most of them are IT students and of course it is non-commercial purpose. Thank you!

[@sushantp25]

Incredible efforts! to be honest i am truly grateful to find this channel ! keep up the good work! thank you so much

[@ByteMonk]

thank you for the comment, keeps me going :)

[@ruturajbhandari7695]

Amazing content. I hope You Reach Millions of subscribers

[@mylaidbacklife]

It took 200 mins to watch but everything explained really well

[@prokhorov_sergey_igorevich]

Did you mean with repeats?

[@electrolyteorb]

You mean seconds?

[@lazerbaconpro]

Excellent video.

[@amitanshusahu1079]

Love this .. explanation, use cases, when not use every thing was covered 10/10

[@abhiydv8624]

awesome explanation, thank you

[@dinesh.p8642]

gold content. thank you!!

[@therevealerDev]

This is very clear and easy to understand. Thanks!

[@fabianleon7640]

Really well represented, thanks for sharing

[@shahfaisal3923]

You won a subscriber from Afghanistan. Great Video.

[@Mayaadyby.]

So clear & well described 👌

[@hmbil694]

This is A-tier content. Keep up the good work!

[@pfever]

Amazing simple explanation, subscribed :)

[@jagritbhupal5836]

Nice video, Thank you!

[@rohith8269]

Great video. Keep going!

[@afrikanonyma]

Great ! If possible to make a longer video about its usecases, like a small tuto ?

[@ByteMonk]

thank you for the suggestion

[@ibrahimnaser5233]

cool, very simple explanation 👍

[@satyanarayandalei-rz2kw]

That was awesome explanation.

[@lunaq3681]

appreciate your work thanks a ton

[@Max-ot2jc]

Thanks! Really useful

[@Jai-xq5hi]

Wonderful explanation ❤

[@maedalnatour1516]

Amazing 👌

[@KDOERAK]

excellent👍

[@Lottielogic]

Loved this!

[@raghavaggarwal9093]

Nicely explained

[@py7432]

WS is like an additional layer of protocol on top of http/s, however browser supports client server due to security reasons so how the socket able to send request from the server to the client?

[@ByteMonk]

please checkout the deep dive video, link in pinned comment/description

[@quintencabo]

Nice video!

[@ahmedghallab5342]

شكرا thanks

[@MuhammadBilal-cs3dg]

Amazing content

[@jairajsahgal7101]

thank you

[@Curious_Citizen0]

good one!!

[@wassup102]

thanks

[@danushadhaamarasekera7215]

thank you brother

[@GalGreen]

It was a nice video, but it barely explained "How Web Sockets work", only in 3:45 to 4:18. Almost all of the video was actually about "What are Web Sockets", focusing mainly on a comparison between polling and sockets, which was well presented, but wasn't supposed to be the topic of the video promised by the title.

[@snuffbox2006]

it is important to know the motivation for why web socket exists before we learn web sockets. What problem is it solving and why do we need it?

[@martinabeita8852]

nicely explained

[@henryl7421]

this is gold info

[@henryl7421]

thank you for doing this!!

[@henryl7421]

I will tell everyone about this channel

[@ByteMonk]

@@henryl7421 Thank you for supporting my work 🙏, this will keep me going

[@blueboy-tm]

Nice thanks bro

[@supersoniqamanyi3075]

Great great

[@Truth_Taken]

Great

[@santoshbhat7847]

How do you create animations ?

[@Mr.Motion.]

With the help of Adobe after effects.

[@aaAaa-rq2cj]

What tool u used for animation in the video

[@popguy2046]

whats the best way to track websocket payload acknowledgement from frontend? (given we can't do it with the same websocket connection)

[@ByteMonk]

When you cannot directly track WebSocket payload acknowledgments using the same WebSocket connection, you can implement a custom acknowledgment mechanism using a combination of techniques. 1. Create a Unique Identifier for Each Payload: Before sending a payload from the frontend, assign a unique identifier (message ID) to each payload. This ID will help you correlate the acknowledgments received from the backend with the original payloads sent from the frontend. 2. Use a Separate Channel for Acknowledgments: Set up a separate communication channel between the frontend and backend. This can be another WebSocket connection, an HTTP REST API, or any other messaging protocol that suits your application. 3. Send Payloads and Wait for Acknowledgments: When sending a payload from the frontend to the backend via the primary WebSocket connection, store the payload's unique identifier along with its content in a local data structure (e.g., a map). 4. Backend Processing and Acknowledgment: On the backend, process the received payload and perform the required actions. After the backend has processed the payload successfully, it sends an acknowledgment message back to the frontend via the separate communication channel, containing the unique identifier of the processed payload. 5. Frontend Acknowledgment Handling: When the frontend receives an acknowledgment, it can use the unique identifier in the acknowledgment message to identify the corresponding payload in the local data structure and mark it as acknowledged. You can remove the entry or update its status in the map.

[@justafreak15able]

Title should have benn HTTP polling 😂

[@ByteMonk]

This was made from system design interview perspective. I have done a part-2 follow up video to deep dive on web sockets , please check that out in my channel

[@saeeduchiha5537]

Almost all apps nowadays have Real Time part in them

[@Apoorvpandey]

Crisp

[@krishna26g]

Who asked you about polling

[@ByteMonk]

No One :)

[@Pablo-hp2jp]

Das Video erklärt viel Kontext, aber leider keine Details zu WebSockets. Schade

[@Zmey5656]

I use WebSocket to get real cryptocurrency data

[@siyaram2855]

1st

[@zixuanzhao6043]

speaking too fast bro

[@ByteMonk]

thanks for the feedback, will work on my pace