16. Real-Time WebSockets Architecture: Socket.io with Redis Adapter Scaling • Node.js Backend Architecture: Libuv to High-Scale Microservices • Rishabh Ki Kaksha

*   **HTTP/1.1 Polling:** Client har 2 second me request bhejta hai: *"Koi naya message hai kya?"* (Heavy network header overhead, wasteful).
*   **WebSockets (`ws://`, `wss://`):** 1 single persistent TCP connection jisme Client aur Server dono bina request ke **Full-Duplex real-time data stream** bhej sakte hain (0.1ms latency!).

---

### 2. The Horizontal Scaling Problem (Multi-Server Broadcast) ⚠️

Agar Server 1 par User A connect hai aur Server 2 par User B connect hai:
*   Jab User A message bhejega, toh Server 1 use Server 2 ke User B tak **nahi bhej sakta** (Kyunki memory isolated hai!).

**Solution: Redis Pub/Sub Adapter Architecture 🌐**

```
[ User A ] ➔ [ Server 1 ] ➔ Redis Pub/Sub ("chat-room") ➔ [ Server 2 ] ➔ [ User B ]
```

---

### 3. Production Socket.io with Redis Adapter Implementation

```typescript
import { createServer } from "http";
import { Server } from "socket.io";
import { createClient } from "redis";
import { createAdapter } from "@socket.io/redis-adapter";

const httpServer = createServer();
const io = new Server(httpServer, {
    cors: { origin: "https://rishabhkikaksha.boostengine.in" }
});

// Redis Pub/Sub Clients
const pubClient = createClient({ url: process.env.REDIS_URL });
const subClient = pubClient.duplicate();

Promise.all([pubClient.connect(), subClient.connect()]).then(() => {
    io.adapter(createAdapter(pubClient, subClient));
    console.log("🌐 Socket.io clustered across Redis Pub/Sub!");
});

io.on("connection", (socket) => {
    socket.on("join-room", (roomId) => socket.join(roomId));

socket.on("send-message", ({ roomId, message }) => {
        // Broadcasts across ALL servers in the cluster!
        io.to(roomId).emit("new-message", message);
    });
});
```

---

### 4. Master Comparison Matrix

---

### 5. Interview Ke 3 Sawal Is Topic Se

1. **WebSocket Handshake process kaise execute hota hai?** -> Client HTTP `GET` request bhejta hai with headers `Upgrade: websocket` aur `Connection: Upgrade`; Server `101 Switching Protocols` return karke TCP socket ko WebSocket me upgrade kar deta hai.
2. **WebSocket connections ke sath Load Balancer configure karte waqt Sticky Sessions kyu zaroori hote hain?** -> HTTP long-polling fallback handshake ke dauran saari initial handshake requests same backend server node par pahunchani zaroori hoti hain.
3. **Heartbeat / Ping-Pong mechanism ka kya purpose hota hai?** -> Inactive dead connections ko detect karke close karna taaki memory leaks na hon aur firewalls/NAT routers connection ko drop na karein.

---
**Next Topic:** 17. Asynchronous Task Queues with Redis & BullMQ (Retries, Backoff, Dead Letters)

Loading lesson content...

JavaScript

Full IDE

Live Execution Terminal

Click "Execute Live" to run code.
                

Lesson Mastery AI Quiz

AI Doubt Solver

CERTIFICATE OF COMPLETION

Rishabh Gehlot

PHP 8+ & Laravel 11 Master Track