Skip to main content

Using WebSockets for Real-Time Communication in Full-Stack Apps

 Using WebSockets for Real-Time Communication in Full-Stack Apps

WebSockets enable real-time, bi-directional communication between the client and server, making them ideal for applications like chat apps, live notifications, collaborative tools, and stock market dashboards. Unlike traditional HTTP requests, WebSockets maintain a persistent connection, reducing latency and improving efficiency.

1. How WebSockets Work

  • A client initiates a WebSocket connection with a handshake request.
  • Once established, the connection remains open, allowing continuous data exchange between the client and server.
  • Both parties can send messages without repeatedly requesting data, unlike HTTP polling.

Key Benefits

✅ Low latency communication
✅ Reduced server load (no repeated requests)
✅ Real-time data streaming
✅ Full-duplex communication (simultaneous sending and receiving of data)

2. Setting Up WebSockets in a Full-Stack App

Frontend (Client-Side) – Using JavaScript

Modern browsers provide a built-in WebSocket API. Here’s how you establish a connection:

const socket = new WebSocket("ws://localhost:5000");

// Listen for messages
socket.onmessage = (event) => {
    console.log("Message from server:", event.data);
};

// Send a message
socket.onopen = () => {
    socket.send("Hello, Server!");
};

// Handle connection close
socket.onclose = () => {
    console.log("WebSocket connection closed");
};

Backend (Server-Side) – Using Node.js & WebSocket Library

Install the WebSocket package:

npm install ws

Create a simple WebSocket server:

const WebSocket = require("ws");
const server = new WebSocket.Server({ port: 5000 });

server.on("connection", (ws) => {
    console.log("Client connected");

    ws.on("message", (message) => {
        console.log("Received:", message);
        ws.send("Server received: " + message);
    });

    ws.on("close", () => {
        console.log("Client disconnected");
    });
});

3. Integrating WebSockets into a Full-Stack App

With Express & WebSockets

If your app already uses Express, you can integrate WebSockets:

const express = require("express");
const http = require("http");
const WebSocket = require("ws");

const app = express();
const server = http.createServer(app);
const wss = new WebSocket.Server({ server });

wss.on("connection", (ws) => {
    ws.send("Welcome to the WebSocket Server!");
    ws.on("message", (message) => {
        console.log("Received:", message);
        ws.send(`Echo: ${message}`);
    });
});

app.get("/", (req, res) => {
    res.send("WebSocket server is running");
});

server.listen(5000, () => console.log("Server running on port 5000"));

4. Use Cases for WebSockets in Full-Stack Apps

🔹 Chat Applications – Real-time messaging between users
🔹 Live Notifications – Instant alerts (e.g., social media updates, emails)
🔹 Stock Market Dashboards – Live price updates
🔹 Multiplayer Games – Synchronizing game states
🔹 Collaborative Editing – Real-time text or design collaboration

5. Scaling WebSockets

For large-scale applications, use:

  • Redis Pub/Sub – Sync WebSocket connections across multiple server instances.
  • Socket.io – A WebSocket abstraction with fallback support for older browsers.
  • Load Balancers (NGINX, AWS ALB) – Distribute WebSocket traffic across multiple servers.

Example using Socket.io for easier real-time communication:

const io = require("socket.io")(server);

io.on("connection", (socket) => {
    console.log("User connected:", socket.id);

    socket.on("message", (data) => {
        io.emit("message", data); // Broadcast message to all clients
    });

    socket.on("disconnect", () => {
        console.log("User disconnected");
    });
});

Conclusion

WebSockets provide an efficient way to implement real-time features in full-stack applications. By maintaining a persistent connection, they reduce latency and server load compared to traditional polling methods. Whether for chat apps, live updates, or collaborative tools, WebSockets enhance user experience with instant communication.

For more details 

Popular posts from this blog

What are the different types of directives in Angular? Give real-world examples.

In Angular, directives are classes that allow you to manipulate the DOM or component behavior . There are three main types of directives: 🧱 1. Component Directives Technically, components are directives with a template. They control a section of the screen (UI) and encapsulate logi c. ✅ Example: @Component ({ selector : 'app-user-card' , template : `<h2>{{ name }}</h2>` }) export class UserCardComponent { name = 'Alice' ; } 📌 Real-World Use: A ProductCardComponent showing product details on an e-commerce site. A ChatMessageComponent displaying individual messages in a chat app. ⚙️ 2. Structural Directives These change the DOM layout by adding or removing elements. ✅ Built-in Examples: *ngIf : Conditionally includes a template. *ngFor : Iterates over a list and renders template for each item. *ngSwitch : Switches views based on a condition. 📌 Real-World Use: < div * ngIf = "user.isLoggedIn...
Read more

Explain the Angular compilation process: View Engine vs. Ivy.

 The Angular compilation process transforms your Angular templates and components into efficient JavaScript code that the browser can execute. Over time, Angular has evolved from the View Engine compiler to a newer, more efficient system called Ivy . Here's a breakdown of the differences between View Engine and Ivy , and how each affects the compilation process: 🔧 1. What Is Angular Compilation? Angular templates ( HTML inside components) are not regular HTML—they include Angular-specific syntax like *ngIf , {{ }} interpolation, and custom directives. The compiler translates these templates into JavaScript instructions that render and update the DOM. Angular uses Ahead-of-Time (AOT) or Just-in-Time (JIT) compilation modes: JIT : Compiles in the browser at runtime (used in development). AOT : Compiles at build time into efficient JS (used in production). 🧱 2. View Engine (Legacy Compiler) ➤ Used in Angular versions < 9 🔍 How It Works: Compiles templat...
Read more

What is Zone.js, and why does Angular rely on it?

Zone.js is a library that Angular relies on to manage asynchronous operations and automatically trigger change detection when necessary. Think of it as a wrapper around JavaScript’s async APIs (like setTimeout , Promise , addEventListener , etc.) that helps Angular know when your app's state might have changed. 🔍 What is Zone.js? Zone.js creates an execution context called a "Zone" that persists across async tasks. It tracks when tasks are scheduled and completed—something JavaScript doesn't do natively. Without Zone.js, Angular wouldn’t automatically know when user interactions or async events (like an HTTP response) occur. You’d have to manually tell Angular to update the UI. ⚙️ Why Angular Uses Zone.js ✅ 1. Automatic Change Detection Zone.js lets Angular detect when an async task finishes and automatically run change detection to update the UI accordingly. Example: ts setTimeout ( () => { this . value = 'Updated!' ; // Angular know...
Read more