---
title: "Discussion on \"Three Restaurants, One Kitchen: What Broke When it Scaled\" | Hashnode"
description: "Discussion on \"Three Restaurants, One Kitchen: What Broke When it Scaled\". A follow-up on why a WebSocket pattern that worked great on one pod quietly broke at three, and how Redis pub/sub fixed it."
url: "https://hashnode.com/posts/three-restaurants-one-kitchen-what-broke-when-it-scaled/6a80a7cde2ceabe01cf5a776"
---

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

Discussion

# [Three Restaurants, One Kitchen: What Broke When it Scaled](https://kunalforked.hashnode.dev/three-restaurants-one-kitchen-what-broke-when-it-scaled?utm_source=hashnode&utm_medium=feed)

A follow-up on why a WebSocket pattern that worked great on one pod quietly broke at three, and how Redis pub/sub fixed it.

Aug 15 · 5 min read · kunalforked.hashnode.dev  
Read the article

-   [#redis](https://hashnode.com/tag/redis)
-   [#websocket](https://hashnode.com/tag/websocket)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#python](https://hashnode.com/tag/python)
-   [#backend](https://hashnode.com/tag/backend)

## Written by

[Kunal Gupta](https://hashnode.com/@kunalforked)

@kunalforked · Bengaluru, India

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

Software Engineer, Tech Enthusiast

I'm a backend engineer who spends most days deep in distributed systems, services talking to each other, breaking in interesting ways, and occasionally behaving. I write here about what I actually learn while building and debugging things, not the polished version.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
