WebSockets With Nodejs

Hello Developers, I hope you are doing good. Today we will look at what WebSocket is? You may have heard about real-time data during your learning process or work. Real-Time data is delivered immediately after collection. There is no delay in the transmission of the data. Real-time data is often used for navigation, tracking, gaming, communications etc., where your user interface does not refresh frequently.

When there is communication between the two systems, we follow some protocols. The protocol is a set of rules that allow two or more entities or machines of a communications system to transmit information via any kind of variation of a physical quantity. It defines the syntaxes, rules, semantics and synchronization of communication and effective error recovery techniques.

There are many types of protocols we can follow for communication between two or more systems. The most used communication protocol is the HTTPS protocol. But if you want real-time & quick data transfer, HTTPS is not recommended.

The WebSockets protocol is completely different from the HTTP or HTTPS protocol. After the initial handshake occurs over HTTP, there is no more notion of HTTP related things, for example, cookies.

The major con of HTTPS for real-time data transfer is that HTTPS is unidirectional. That means, when you have to do communication, it always opens the connection, does its processing, and returns with some response by closing the connection. For real-time data, it is too much processing. To avoid this, we can go with WebSockets.

The WebSocket connection is a persistent connection between a client app and the server. The server can send messages to the client, and the client sends its response back with the same connection, which is created initially. It allows the server and client to communicate in an asynchronous way. The server and client can communicate and acknowledge or exchange the data at the same time. WebSocket helps to create real-time communication between web servers and clients.

The WebSocket connection is a persistent connection between a client app and the server. The server can send messages to the client and the client sends its response back with the same connection which is created initially. It allows the server and client to communicate in an asynchronous way. The server and client can communicate and acknowledge or exchange the data at the same time. WebSocket helps to create real-time communication between web servers and clients.

So now, the question is, How can we implement WebSockets?

There are many ways out of these we prefer to go with “ socket.io.” It is a library that allows us to do real-time, bidirectional, and event-based communication between the browser and the server, which is based on Node.js and a Javascript client library for the browser. It is the wrapper around the WebSocket API. The best part of socket.io library is –

It supports almost all browsers (97%), that are available today

There is no element (proxy, firewall, …) preventing WebSocket connections between the client and the server.

Server-side code snippet to set up Websocket.io –

const io = require('socket.io')(3000);

io.on('connect', socket => {
// either with send()
socket.send('Hello!');

// or with emit() and custom event names
socket.emit('greetings', 'Hey!', { 'dr': 'anna' }, Buffer.from([4, 3, 3, 1]));

// handle the event sent with socket.send()
socket.on('message', (data) => {
console.log(data);
});

// handle the event sent with socket.emit()
socket.on('salutations', (elem1, elem2, elem3) => {
console.log(elem1, elem2, elem3);
});
});

Client-side code snippet to set up Websocket.io –

const socket = io('ws://localhost:3000');
socket.on('connect', () => {

// either with send()

socket.send('Hello!');
// or with emit() and custom event names
socket.emit('salutations', 'Hello!', { 'dr': 'jordan' }, Uint8Array.from([1, 2, 3, 4]));

});
// handle the event sent with socket.send()

socket.on('message', data => {

console.log(data);

});
// handle the event sent with socket.emit()

socket.on('greetings', (elem1, elem2, elem3) => {

console.log(elem1, elem2, elem3);

});

Why using ‘socket.io’ library is best –

• Better Reliability
• Auto-reconnection support
• Disconnection detection
• Binary support
• Multiplexing support

For more details, what is better than official documentation! Do check the official doc at https://socket.io/

Quick Demo –

Do check the live demo at – https://socket-io-chat-app-demo.herokuapp.com/
Find code for above demo at – https://github.com/nikhil-jaunjal/socket.io-chat-app