---
title: "Discussion on \"The bottleneck didn’t go away. It moved.\" | Hashnode"
description: "Discussion on \"The bottleneck didn’t go away. It moved.\". I moved the ticket counter from Postgres into Redis. The hot row was gone, but one Node process became the new limit, until more workers took it from 1,000 to 6,000 requests a second."
url: "https://hashnode.com/posts/redis-vs-postgres-flash-sale-scaling/6adc9f532315aa7dc534af0e"
---

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

Discussion

# [The bottleneck didn’t go away. It moved.](https://manideepnaidu.hashnode.dev/redis-vs-postgres-flash-sale-scaling?utm_source=hashnode&utm_medium=feed)

I moved the ticket counter from Postgres into Redis. The hot row was gone, but one Node process became the new limit, until more workers took it from 1,000 to 6,000 requests a second.

Oct 24 · 7 min read · manideepnaidu.hashnode.dev  
Read the article

-   [#redis](https://hashnode.com/tag/redis)
-   [#postgres](https://hashnode.com/tag/postgres)
-   [#nodejs](https://hashnode.com/tag/nodejs)
-   [#performance](https://hashnode.com/tag/performance)
-   [#scaling](https://hashnode.com/tag/scaling)
-   [#system-design](https://hashnode.com/tag/system-design)

## Written by

[Manideep Naidu](https://hashnode.com/@manideepn7)

@manideepn7 · Bangalore, India

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

IIT Patna CSE | Software Engineer@ One-Geo | Ex-Intern Myntra , Success Numbers

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
