Re:Using PostgreSQL as a Dead Letter Queue for Event-Driven ...
by nicoritschel on Sunday January 25, 2026 @01:55PM
(#46756966)
lol a FOR UPDATE SKIP LOCKED post hits the HN homepage every few months it feels like
[ Parent
| on HN ]
Re:Using PostgreSQL as a Dead Letter Queue for Event-Driven ...
by whateveracct on Sunday January 25, 2026 @01:59PM
(#46757007)
and another CTO will use this meme as a reason to "just use Postgres" for far longer than they should lmao
Re:Using PostgreSQL as a Dead Letter Queue for Event-Driven ...
by throw_away_623 on Sunday January 25, 2026 @06:38PM
(#46759848)
I’ll take “just use Postgres” over “prematurely add three new systems” any day. Complexity has a cost too.
Using Postgres too long is probably less harmful than adding unnecessary complexity too early
Re:Using PostgreSQL as a Dead Letter Queue for Event-Driven ...
by whateveracct on Sunday January 25, 2026 @06:58PM
(#46760022)
It probably is, but I don't like to operate as if I will inevitably make giant mistakes. Sometimes there isn't a trade off - you can just be good lolol.
Both are pretty bad.