I wrote this (my own blog). I shipped Nest with the default @nestjs/throttler storage and only noticed the hole when a second instance sat behind the load balancer — each process kept its own counter, so a client that should stop at 100/min quietly got closer to 200.

Retested on Nest 12.3 / throttler 6.7 with limit 100/60s on one box. One process: memory, Redis and Postgres all 429 on request 101. Two processes alternating the same IP: memory allowed all 130; Redis and Postgres stopped at 100. Localhost p50 was 0.36 ms memory, 0.38 ms Redis, 1.00 ms Postgres.

Storage code and tables are in the post. Curious what people use in production when they already have Postgres and don’t want Redis just for counters.