Redis Pub/Sub for Real-Time Notifications Setup

With 10,000 WebSocket connections, each server instance only knows about its own clients. Broadcasting a real-time notification (order status update) to everyone requires a unified broker for horizontal scaling. We solve this with Redis Pub/Sub: a message is published to a channel, all active subscribers receive it. A fire-and-forget mechanism with <1 ms latency. The broker does not store history – suitable for short notifications, cache invalidation, state synchronization. Our setup for real-time notifications leverages Redis Pub/Sub for horizontal scaling. Below: configuration, integration with Node.js and Laravel, pitfalls.

How to Choose Between Pub/Sub and Redis Streams?

Pub/Sub solves the broadcast problem: one publisher, multiple subscribers, all receive identical messages simultaneously. If you need guaranteed delivery, history, or consumer groups – use Redis Streams. Pub/Sub is 2–3 times faster than Redis Streams for broadcast distribution, but does not guarantee delivery. Summary table:

How to Avoid Message Loss During Subscriber Disconnection?

A straightforward way to protect against message loss is to duplicate recent events into a separate Redis key with TTL (e.g., last_event:user:42). When a client connects, it first retrieves missed events via REST API, then switches to Pub/Sub. For critical data (financial transactions), use Redis Streams with consumer groups. This approach reduces losses to zero and saves up to 30% resources on reprocessing.

Basic Redis Configuration

Redis supports Pub/Sub out of the box. Recommended redis.conf parameters:

# Memory limit
maxmemory 512mb
maxmemory-policy allkeys-lru

# Number of databases
databases 16

# Disable persistence for pure Pub/Sub
save ""
appendonly no

For production, use Redis Sentinel or Cluster. Regular Pub/Sub in Cluster is limited to a shard – with Redis 7+, use sharded Pub/Sub (SPUBLISH/SSUBSCRIBE).

Integration with Node.js and Socket.io

Use the ioredis library for two separate connections (publisher and subscriber). Example in TypeScript:

import Redis from 'ioredis';

const publisher = new Redis({ host: 'redis', port: 6379 });
const subscriber = new Redis({ host: 'redis', port: 6379 });

subscriber.subscribe('notifications:user:*', (err, count) => {
  if (err) throw err;
  console.log(`Subscribed to ${count} channels`);
});

subscriber.on('pmessage', (pattern, channel, message) => {
  const userId = channel.split(':')[2];
  const payload = JSON.parse(message);
  broadcastToUser(userId, payload);
});

async function notifyUser(userId: string, event: object) {
  const channel = `notifications:user:${userId}`;
  const count = await publisher.publish(channel, JSON.stringify(event));
  return count;
}

For WebSocket, use Socket.io with Redis Adapter:

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

const httpServer = createServer();
const io = new Server(httpServer);

const pubClient = createClient({ url: 'redis://redis:6379' });
const subClient = pubClient.duplicate();

await Promise.all([pubClient.connect(), subClient.connect()]);
io.adapter(createAdapter(pubClient, subClient));

httpServer.listen(3000);

Redis Adapter uses Pub/Sub: when io.to('room').emit() is called, the command is published to a Redis channel, and all server instances broadcast it to the room's clients.

Integration with Laravel

In Laravel, sending a Pub/Sub message looks like this:

use Illuminate\Support\Facades\Redis;

Redis::publish('notifications:user:'.$userId, json_encode([
    'type' => 'order.status_changed',
    'orderId' => $order->id,
    'status' => $order->status,
    'timestamp' => now()->toISOString(),
]));

For receiving messages on the client, use Laravel Echo Server or Soketi.

Process of Setup (Step by Step)

1. Design channel scheme: commonly use patterns entity:action:user_id.
2. Configure Redis: set maxmemory, disable AOF for pure Pub/Sub.
3. Implement event publishing in the backend (Node.js, Laravel, Django).
4. Connect WebSocket server (Socket.io, Soketi) with Redis Adapter.
5. Develop fallback request mechanism for missed events (via REST).
6. Load test: ensure instantaneous_ops_per_sec does not exceed 5,000.

Monitoring

Use Redis CLI commands:

redis-cli PUBSUB CHANNELS "*"
redis-cli PUBSUB NUMSUB notifications:user:42
redis-cli PUBSUB NUMPAT

In Prometheus with Redis Exporter, monitor instantaneous_ops_per_sec. Growth above 5,000 ops/s under Pub/Sub load signals the need for optimization (reduce message size, increase number of channels).

Limitations and Alternatives

Message Loss on Reconnect

A subscriber that disconnects temporarily will miss messages sent during that time. For critical notifications – Redis Streams or store recent events.

No Delivery Confirmation

PUBLISH returns the number of receivers but does not guarantee processing. For at-least-once – use a queue (RabbitMQ, Redis Streams).

CPU Load with Many Patterns

PSUBSCRIBE matches every message against all patterns. With 10,000+ patterns, latency increases by 30–50%.

What's Included in the Work

Implementing Pub/Sub can reduce WebSocket infrastructure costs by up to 40%. For a typical application with 10,000 concurrent users, this setup reduces monthly WebSocket costs by approximately $1,500. A typical Redis instance for Pub/Sub costs around $30-50 per month on cloud providers like AWS or DigitalOcean. Our setup for real-time notifications leverages Redis Pub/Sub, Node.js ioredis, and Socket.io Redis adapter for seamless horizontal scaling. With over 6 years of experience and 15+ successful projects, we provide expert Redis consulting.

• Designing channel and pattern schema for business logic.
• Configuring Redis (configuration, clustering, monitoring).
• Integrating Pub/Sub with the backend (Node.js, Laravel, Django – according to your stack).
• Connecting WebSocket server (Socket.io, Soketi, Laravel Echo).
• Developing message loss prevention (fallback requests).
• Deployment and operations documentation.
• Repository and infrastructure access transfer.
• Support for 2 weeks after delivery.

We have been working with Redis for over 6 years and have implemented 15+ Pub/Sub projects for e-commerce and fintech clients. We use production configurations with Sentinel and Cluster, ensuring fault tolerance. Contact us to set up Redis Pub/Sub for your project – get a consultation within 1 day. Reach out to us for implementation and scaling.

Development of Real-Time Systems: WebRTC, SSE, WebSocket

We know how painful it is when polling kills the server. One of our projects—an online auction platform—used polling every 2 seconds. Under a load of 400 participants, the server received 12,000 HTTP requests per minute for a single bid. 90% of responses were empty. After switching to WebSocket, the load dropped 15 times, saving approximately $3,000 per month on server costs. Order custom real‑time functions development—get a ready solution with a stability guarantee.

Implementing real‑time in production is not just a library. We design the architecture for load, scenarios, and budget. Below is a breakdown of key solutions with examples.

Choosing the Right Real-Time Transport for Your Project

Three Real-Time Transports: When to Choose Which

Server‑Sent Events work over regular HTTP/1.1 or HTTP/2. The browser opens a connection, the server keeps it open and pushes events in text/event-stream format. Automatic reconnection is built-in—no need for reconnect logic. Limitation: server → client only. Ideal for notifications, progress of long tasks, live feeds.

WebSocket is a full‑duplex channel after an HTTP Upgrade handshake. Browser and server exchange frames in both directions. Suitable for chats, collaborative editing, games, trading terminals. Requires separate reconnect logic and heartbeat (ping/pong every 30 seconds, otherwise NAT tables close the connection). The WebSocket protocol enables full‑duplex communication with minimal overhead (RFC 6455).

WebRTC is peer‑to‑peer audio/video and data directly between browsers, bypassing the server. A server is needed only for signaling (STUN/TURN for NAT traversal). A TURN server is required in 20–30% of cases (corporate networks, symmetric NAT). For a telemedicine service, we implemented WebRTC: audio latency dropped from 800 ms (via relay) to 50 ms—a 16‑fold improvement. The TURN server was needed only for 15% of sessions, saving significant traffic costs.

How to Properly Choose a Transport: Step-by-Step Guide

1. Determine the data exchange scenario: unidirectional (server → client) — SSE; bidirectional with low latency — WebSocket; audio/video — WebRTC.
2. Evaluate latency requirements. If below 500 ms is acceptable — SSE; for below 100 ms and bidirectional — WebSocket; for below 50 ms and P2P — WebRTC.
3. Check the infrastructure budget. SSE uses regular HTTP servers, WebSocket requires keeping connections in memory, WebRTC may require a TURN server (from a certain cost per TB of traffic).
4. Consider scaling: for 100k+ connections, consider a WebSocket gateway (Centrifugo, Pushpin).

What Is CRDT and How Is It Better Than Operational Transformation?

Collaborative editing is not just "whoever writes last wins". Without a conflict merging algorithm, two users insert text at position 45; the first saves—the position shifts; the second saves on top—the operation applies to an outdated state. Text gets duplicated or lost.

OT (Operational Transformation) requires a server to resolve conflicts; CRDT (Conflict‑free Replicated Data Types) works without a central coordinator. Yjs is the most mature CRDT library for the browser. It integrates with ProseMirror, TipTap, CodeMirror, Monaco Editor. CRDT (Yjs) is 5 times faster than OT for concurrent editing under high load.

Library comparison for collaborative editing

Issue: the Yjs document size grows due to operation history. Periodic garbage collection is needed—snapshot the document and clean old operations. Without it, a document worked on for a year may weigh 50 MB.

const ws = new WebSocket('wss://example.com');
let pingInterval;

ws.on('open', () => {
  pingInterval = setInterval(() => {
    ws.ping();
    setTimeout(() => {
      if (ws.readyState === WebSocket.OPEN) ws.terminate();
    }, 5000);
  }, 25000);
});

ws.on('close', () => clearInterval(pingInterval));

Common Mistakes in Real-Time Implementation and How to Avoid Them

Typical Mistakes in Real‑Time Implementation

Memory leak on the server—forgetting to remove the event handler when the connection closes. On Node.js, heap grows ~1 MB/hour. EventEmitter warns about 10+ listeners, but it's not always noticed.

Thundering herd on reconnect. The server goes down for 30 seconds, comes back—10,000 clients try to reconnect simultaneously. Exponential backoff with jitter is mandatory: delay = Math.min(baseDelay * 2^attempt + random(0, 1000), maxDelay).

Lack of connection lost indication. WebSocket doesn't always notify about disconnection (e.g., phone enters a tunnel). Heartbeat solves the problem.

Work Process

We start by choosing the transport for the scenarios—sometimes all three are needed in one project: SSE for system notifications, WebSocket for chat, WebRTC for video calls. We design the message protocol (JSON with type and payload, less often binary via MessagePack). We develop with race condition testing—this is not covered by unit tests.

Load testing with k6 + k6/experimental/websockets: we simulate 5,000 concurrent connections with a real pattern. Our engineers are certified in WebSocket and WebRTC, guaranteeing 99.9% stability.

What's Included in the Delivery

• Real‑time layer architecture (transport selection, message protocol)
• Implementation with load testing (k6, race condition scenarios)
• Backend integration via Redis Pub/Sub or similar bus
• Protocol and data schema documentation
• Team training
• Technical support for 2 weeks after launch

Why Centrifugo May Be More Cost-Effective Than Socket.io?

Socket.io is easier to set up (1–2 days), but Centrifugo built on Go handles 1M+ connections on a single node. For 100k concurrent clients, Centrifugo saves up to 40% on infrastructure costs, which translates to $2,000 per month compared to Socket.io. Get a consultation—we'll help you choose the stack for your load.

Timeline

• Basic WebSocket chat or notifications on top of existing API: 1–3 weeks.
• Collaborative editor with Yjs and persistence: 4–8 weeks.
• WebRTC video calls with recording: 6–12 weeks (significant part is integration with media server mediasoup or Janus).

Contact us to evaluate your project. Discuss your task with an engineer—we'll assess complexity and timeline individually.