Pusher integration for real-time website notifications

Real-time notifications are not a luxury but a necessity for modern web applications. Organizing a reliable WebSocket channel under load is complex: you need to manage thousands of connections, handle disconnections, configure authorization, and scale infrastructure. We solved this problem on more than 40 projects across various industries: from online stores to financial platforms. We settled on Pusher — a managed service that handles all WebSocket work, providing latency under 50 ms and 99.9% availability.

A typical scenario: an online store receives a new order — the manager needs to see it instantly to start processing. Ordinary HTTP polling creates delays of several seconds and extra server load. With Pusher, the event arrives in 30–50 ms, and the system automatically reconnects on failure. No headache with your own WebSocket servers — everything is managed from the cloud.

We have prepared a ready-made architecture: the server publishes events via HTTP API with a single command, the client subscribes to channels via JavaScript SDK. Everything else — connection management, server clustering, error recovery — is handled by Pusher with 99.9% SLA. This architecture easily scales to tens of thousands of simultaneous connections without code changes.

How does Pusher integration work?

The client subscribes to channels, the server publishes events via HTTP API. Pusher manages connections, clustering, and error recovery on its own. The developer only needs to define channel logic and authorization.

Key problems we solve

Notification delays

Pusher provides latency under 50 ms under average load. For online stores, it's critical to instantly notify the manager about a new order — Pusher delivers the event faster than your own WebSocket server on an average VPS.

Access authorization

Private channels require permission checks. We implement an endpoint /pusher/auth that verifies authentication and returns a signature for subscription. Only authorized users receive private notifications.

Online statuses

Presence channels allow tracking who is currently in a chat or room. Pusher automatically fires member_added and member_removed events, along with the current member list.

How we do it: stack and configs

Server side (Laravel / Node.js)

For Laravel we use the pusher-php-server package:

use Pusher\Pusher;

$pusher = new Pusher(
    config('pusher.key'),
    config('pusher.secret'),
    config('pusher.app_id'),
    ['cluster' => config('pusher.cluster'), 'useTLS' => true]
);

For Node.js we use the official library as shown in the example below.

Client side (React / Next.js)

We provide a ready-made React hook useOrderNotifications that automatically connects to Pusher, listens for events, and displays toast notifications. The hook is SSR-safe because it initializes only on the client.

Integration example in TypeScript

import Pusher from 'pusher';

const pusher = new Pusher({
  appId: process.env.PUSHER_APP_ID,
  key: process.env.PUSHER_KEY,
  secret: process.env.PUSHER_SECRET,
  cluster: process.env.PUSHER_CLUSTER,
  useTLS: true
});

async function notifyOrderUpdate(orderId: string, status: string, userId: string) {
  await pusher.trigger(`private-user-${userId}`, 'order-updated', {
    orderId,
    status,
    timestamp: new Date().toISOString()
  });
}

app.post('/pusher/auth', authenticate, (req, res) => {
  const { socket_id, channel_name } = req.body;
  const userId = req.user.id;

  if (channel_name !== `private-user-${userId}`) {
    return res.status(403).json({ error: 'Forbidden' });
  }

  const auth = pusher.authorizeChannel(socket_id, channel_name);
  res.json(auth);
});

Pusher vs self-hosted alternatives

Pusher wins in speed of deployment and reliability — self-hosted solutions require load balancer setup, monitoring, and backup. Moreover, Pusher saves up to $5,000 per year on infrastructure and administration.

Pusher channel types

Workflow

1. Analysis — define notification types, channels, and access rights.
2. Design — design event structure and authorization.
3. Implementation — server-side (authorization, publishing) and client-side (subscription, handling).
4. Testing — verify authorization correctness, load testing.
5. Deploy — set up CI/CD, monitoring.

Timeline: basic integration — 2–3 days; with presence channels and multiple event types — up to 5 days.

What's included

• Pusher account registration and cluster configuration.
• Server-side private channel authorization (REST endpoint).
• Client component development (React hooks, Vue composables).
• Integration with existing authentication system.
• Documentation on channels and events.
• Deployment and monitoring instructions (Pusher dashboard metrics).

Why choose Pusher?

• Simplicity — intuitive API, documentation with examples.
• Reliability — 99.9% SLA, automatic recovery.
• Compatibility — works with any stack (Laravel, Node.js, Django, React, Vue).

We guarantee that integration won't require rewriting existing logic — Pusher easily integrates into any architecture. Request a consultation — we'll find the optimal channel configuration and implement turnkey integration. Contact us to assess your project.

Conclusion

Pusher is a ready-made solution for real-time notifications that saves weeks of development and up to $5,000 per year. Leverage our experience — get a consultation and start integration today.

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.