---
title: "Discussion on \"Socket. + Redis in Production: Scaling Realtime Systems (Pub/Sub vs Streams)\" | Hashnode"
description: "Discussion on \"Socket. + Redis in Production: Scaling Realtime Systems (Pub/Sub vs Streams)\". Real-time features are often treated like a frontend trick: open a socket, emit an event, update the UI, done. That works for a demo—but it breaks quickly once traffic grows, multiple servers enter th"
url: "https://hashnode.com/posts/socket-redis-in-production-scaling-realtime-systems-pub-sub-vs-streams/6a046272e044f035ba0390f6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Socket. + Redis in Production: Scaling Realtime Systems (Pub/Sub vs Streams)](https://performance-app.hashnode.dev/socket-redis-in-production-scaling-realtime-systems-pub-sub-vs-streams?utm_source=hashnode&utm_medium=feed)

Real-time features are often treated like a frontend trick: open a socket, emit an event, update the UI, done. That works for a demo—but it breaks quickly once traffic grows, multiple servers enter th

May 13 · 6 min read · performance-app.hashnode.dev  
Read the article

## Written by

[Navjot Suman](https://hashnode.com/@navjotsuman)

@navjotsuman

  
[View profile](https://hashnode.com/@navjotsuman)

Javascript Developer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.