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

How does BGP prevent routing loops? Explain AS_PATH and loop prevention mechanisms.

 In Border Gateway Protocol (BGP), preventing routing loops is critical — especially because BGP is the inter-domain routing protocol used to connect Autonomous Systems (ASes) on the internet. πŸ”„ How BGP Prevents Routing Loops The main mechanism BGP uses is the AS_PATH attribute . πŸ” What is AS_PATH? AS_PATH is a BGP path attribute that lists the sequence of Autonomous Systems (AS numbers) a route has traversed. Each time a route is advertised across an AS boundary, the local AS number is prepended to the AS_PATH. Example: If AS 65001 → AS 65002 → AS 65003 is the route a prefix has taken, the AS_PATH will look like: makefile AS_PATH: 65003 65002 65001 It’s prepended in reverse order — so the last AS is first . 🚫 Loop Prevention Using AS_PATH ✅ Core Mechanism: BGP routers reject any route advertisement that contains their own AS number in the AS_PATH. πŸ” Why It Works: If a route makes its way back to an AS that’s already in the AS_PATH , that AS kno...

What’s the impact of BGP full routes on router memory and performance?

Receiving full BGP routes (i.e., the full global BGP routing table) has a significant impact on a router's memory and performance. Here's a breakdown of the key impacts: πŸ”§ 1. Memory Usage (RAM) A full BGP table typically contains ~1 million IPv4 routes and growing (~200k+ IPv6 routes). Each BGP route consumes tens to hundreds of bytes of memory, depending on attributes (AS path, communities, etc.). This translates to hundreds of megabytes to several gigabytes of RAM just for storing the BGP RIB (Routing Information Base). The FIB (Forwarding Information Base) , which is installed into the router's hardware or kernel for actual packet forwarding, also consumes memory (especially in TCAM for hardware routers). ❗ Example A router might require 4–8 GB of RAM (or more) to comfortably handle full BGP routes with headroom for growth and stability. 🧠 2. CPU Utilization High CPU load during: Initial BGP session establishment (parsing all rout...

Explain the OSPF LSDB (Link State Database) and how SPF (Shortest Path First) algorithm works.

OSPF (Open Shortest Path First) is a link-state routing protocol , and the LSDB (Link-State Database) and SPF (Shortest Path First) algorithm are core to how OSPF calculates the best paths . Let’s break them down. 🧠 What is the OSPF LSDB (Link-State Database)? The LSDB is a map of the entire OSPF network area — each router stores a complete topology of its area. πŸ” Details: Built from LSAs (Link-State Advertisements) exchanged between routers. Contains info about: Routers and their interfaces Network segments Neighbor relationships Each OSPF router maintains an identical LSDB within the same area. ✅ Key Characteristics: Feature Description Scope One LSDB per OSPF area Source Built from received LSAs Consistency All routers in an area have identical LSDBs Purpose Used as input for SPF algorithm to calculate best paths ⚙️ How the SPF Algorithm Works in OSPF OSPF uses Dijkstra’s Shortest Path First (SPF) algorithm to compute the shortest (lowest-cost)...