Video

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. 👏

Great video! You broke down the topics well, I find myself understanding RSC and this new model well on one day and lost the next but I think you broke it down efficiently! Will definitely be rewatching 😁

Such a quality content there! 👍 Websocket has been overwhelming for me as a socket io user, and this expalins a very decent way love it. I really hope to see more educational contents like this from this channel and alst but not least Ably looks really interesting to give a try too!

Hi I'm Ariful Islam leeton im software developer and website developer and co founder open A. I

You the man!

10/10

I think you should run a test with a single mid-tier server and see where the average limit of WS connections would be.

Many thanks ! Would also love to see how to implement Ably websockets in a Next.JS app :)

Ably is nice, we are just implementing now in one app to build chat and track realtime locations from drivers and sending data to backend with ably queues and work very well.

Awesome tutorial! I think I’m missing something. You’ve added useref to stop it rerendering but why does it re render so much in the first place? I thought react components only re render if state or props change?

It's a great strategy to shine the drawbacks of websocket so you can redirect the people to your managed services with hiding this purpose.

too good to be true : )

Why do we use useRef and not useCallback at 57:00?

I have 3 instances with LB and kafka, when i send the request to kafka server return 200, but on front-end we need to send the response probably via web-socket and this event can be processed on another server. So how front-end can know to which server need to subscribe to socket if we are using LB?