Coding a Simple WebSocket Server in Node.js that Scales!

A quick intro into coding a basic WebSocket server using the fast and efficient NPM package ws.

Don't forget to like this video and subscribe to our channel – we're publishing more videos and walkthroughs every week. Comment below and let us know what you'd like to see next!

[dashaxedit]

We need more of the websocket lessons. Thank you, really apppreciate it. So much production-related use cases we are in demand of. Please make more videos! For example, how to send messages in controllers, how to separate websocket, how to authenticate etc. etc.

[abhilashmukherjee]

Really appreciate how you explained everything from scratch. Helped me build the basic intuition of websockets. Keep doing the good work. Cheers

[datalyrics]

Everything is here. Not too much not too little and also the explanations for productive use are super. However, I admit that I always had to stop. The speed is ok nonetheless. Thank you very much for your effort. Without your video and GPT I would not be where I am now in 4 weeks!

[WrestlingTournamentsDotCom]

Hey Matt, good video, thank you for all your help. A suggestion for future videos, maybe zoom out a bit and make the window you're coding in a bit bigger; it would help me to see more of the code at once. Thank you.

[stockanalogy]

increase your sound in the video i will start watching your videos, you are creating quality content just keep it up, whenever I watch videos from this channel I have seen to grow their channel much faster after my continue watch. Quality content attracts me and youtube recommends that

[erice.]

could you do a video on amqplib and rabbitMQ?

[Varun-msiv]

Thank you for the tutorial very simple and very informative. Can you please share the resources you used to know about ws other than ws-docs.

[marvelfancollection]

Bro great video..however can you increase your audio volume in future videos please..tx

[thomas-sinkala]

At 8:33, you talked about auth, can you make video about this part?

Thank you.

[paulojo]

My react app is unable to connect, am getting response 404 status

[andrewandrosow]

Hello! I tried to write a simple (non-scalable) web server. But there are in satellite phone networks a connection can be destroyed unexpectedly - but a channel of data transmission in phone stay alive (an indicator on a phone show that data transmission in action) . When a server sending ping to a client each minute (for example) - you can set timeout and kill the connection when a response has`n been received. But a client think - the connection is alive... In my opinion - the solution is the next: we can send from a frontend (browser) pings periodically and responding by a server. Timeout mechanisms must be on both sides: s frontend side and a backend side. But a browser hasn't any event handlers for websocket`s 'ping'. It also can't sends pings to server (a browser only responding on websocket pings) . In fact, I can`t listen 'ping' on a browser side. It`s a disadvantage. Classical TCP Socket in Nodejs can sending keep-alive events from a client or from a server side

[mqdylju]

Why do you use --save for, that is completely useless.

[mqdylju]

Can't trust somebody who is constantly looking at his notes, lol!