(www.recall.ai)

570 points davidgu | 1 comments | 07 Jul 25 14:05 UTC | HN request time: 0.426s | source

Show context

deadbabe ◴[11 Jul 25 00:03 UTC] No.44527057[source]▶

Honestly this article is ridiculous. Most people do not have tens of thousands of concurrent writers. And most applications out there are read heavy, not write. Which means you probably have read replicas distributing loads.

Use LISTEN/NOTIFY. You will get a lot of utility out of it before you’re anywhere close to these problems.

replies(2): >>44527789 #>>44549312 #

1. konsalexee ◴[13 Jul 25 10:50 UTC] No.44549312[source]▶

>>44527057 #

I think the title is stating this: "Postgres LISTEN/NOTIFY does not scale"

That means for moderate cases you do not even have to care about this. 99% of PostgreSQL instances out there are not big "scale".

As a sr. engineer is your responsibility to make a decision if you will build for "scale" from day zero or ignore this as you are mindful that this will not affect you until a certain point.

↑