วีดีโอ

am i only the one or the video is stuttering

You have saved my time broo❤❤❤ I have been trying this web socket for my lan based chat app. Now only I could complete that. Credits to you🎉

What theme are you using. Great tutorial by the way, just wandering why you avoided using SocketIO?

Is it optimum to horizontally scale web socket servers with a load balancer in front of them? I might be wrong but how would the load balancer maintain a persistent connection between the client and the final node, does it create two different WebSocket connections, one with the client and another with the final node? If so wouldn't that easily choke the load balancer, or is there any way load balancer connects the final node and client?

Why do you have two http servers running? One is for the handshake of websocket, the other is launched from vite for react frontend. Is this the correct way to handle the websocket?

Thanks

I want to ask if you hve a course on nodejs? You simplify things alot and I am loving it

Light mode is crazy

amazing video this legit a gift from the youtube recomndations

The question of "how many maximum socket connections can one server support?" is actually not about CPU utilization, or memory usage, but rather related to how sockets are handled from network point of view, and you didn't answer this question.

Is Websocket connection is directly between client and server? If no and client have websocket connection from client to LB and LB to server, then how does LB is different than vertical scaling? I am considering my server is light weight as LB, so its resources are only used to maintain the websocket connection and passing messages to client.

First and foremost it was good explanation on the complexity of WebSocket connections horizontal scaling. I wish i had seen this video before, instead of days spending on actual debugging and experiencing these failures on my own. But i do find that every video and blog about scaling WebSocket's use the same chat app example, where we need to broadcast messages amongst many clients. This is a typical use case. It would be helpful to get to know the architecture of solving these issues. Please share if any. Broadcasting is one of the challenges, there are many others like for example, pushing events to one specific client based on any key(Basically routing challenges to a single client where clients are connected to different servers in a distributed systems ). Would be helpful if any related post or blog can be referenced!! Thanks in Advance.

So easy to follow and explained every step! Best cursor WebSocket video out there. Thank you!!!

i liked how you just keep the details away and talk the big picture . great video for the big picture

hugely exciting and great to see!

oke deh

Need the scaling video! Great content of course.

Hi, I am struggling with one concept... Ably allows data to be streamed.. but a lot of data is change in state (i.e, not the full snapshot). So ideally there should be a database which includes current status of each match and odds and this will be used to display all the relevant info regarding match and bets at the time of login/page reload. Any future changes/updates/new bets can be pushed via Ably channels. Have I got that right? or Have I missed something

Very insightful video indeed, great work.

Ty

thank u buddy for creating this awsm content , easy to understand thanks again

*promo sm*

what if your users are actually devices which need always be connected.

thanks for the nice video. Could you share your thoughts of choosing redis over other Dbs and would you like to persist the state data to disk ?

Thank you for helpful video! I have a question regarding horizontal scaling websicket implementation. Is it possible to create a lookup table that maps roomId, which is often used in chat applications, and server id so that users having the same roomId are navigated to connect to the same server when load balancing?

could you please use dark theme! 😅

Could you elaborate a bit on how the Redis based approach works when scaling out?

Thanks for the tutorial, I really appreciate the effort. One q tho, r u rly using white mode in vs code?

I had this exact question and I KNEW (felt it in my bones) that the answer wouldn’t be so simple as having just saying “yeah Only like 100”, thanks for the insight!

Thanks for a great tutorial. Appreciate it.

I’m the author of react-use-websocket, and stumbled on this video. Your kind words made my weekend!❤

Extremely useful, easy to understand, perfect ^)

Amazing video....thanks But you still did not answer the question. How many active websocket connections can a an avg ec2 server hold... or please give a rough ball park estimate range .... This info can be used to decide how many servers we need right ?

This is HIGH-level content, 10/10 quality, 10/10 content, I'm shocked by the low viewership, I wish you all the best on your journey as a content creator

Why cant we use redis instead of websocket?

This guy is a monster, a psychopath, he uses light theme,

Underrated channel.

I'm currently developing an app that highly uses websockets and you have really given me a few insights to think about. Thank you so much for this valuable info 😊

Surprisingly this is one of the only videos I found that actually goes into specifics of this topic. 👍 All other videos and docs are kind handy-wavy.

Is it possible to attach files to the chat?

I think this video would be much more valuable if you could talk more details about how the horizontally scaled system works for a chat app. Everybody knows horizontal scaling is the way to go.

Super!! Its a gamer changer now. Please make it for cakephp 5! Please provide package which easily integrate with cakephp 5

If all your servers use a shared redis instance to communicate with each other, don't we just reintroduce the original problem of a single server handling all the load (defeating the purpose of the load balancer)? I see that it still helps, since non-websocket work is still distributed, but at scale, I dont see how anything is solved. Especially for apps like chat apps where the websockets carry a lot of the work. Great video though!

Awesome thing but my eyes are crying with this light IDE 😂

Good video. I have one question - in you research, did you found a smooth way to pass data from client component to server component? Lets say, user click on an item in the table and a table footer pops up with more data about the row that was clicked in the table. I want the "more data" to be fetched and displayed in server component. But for the server component to know what data to fetch it need the row id which is stored in state management system Zustand (runs only on client).... So how can i pass the newly selected ID to server compoennt?

High quality content! Looking for a real-life tutorial on horizontally scaling web sockets

isnt this just web sockets......

Please I need your assistance

Awesome video - clear and concise. 👏