build, lift, & coffee | ENS Steward | namestone.com | slobo.xyz

something tells me whoever made this hasn’t used redis or rabbitmq

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

I wrote a book on rabbitmq back in the day, just use postgres

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

postgres for queue management?? i've never actually used rabbitmq but redis (via bullmq) feels much nicer than whatever i'd try to build in postgres

pgmq: https://github.com/pgmq/pgmq

lightweight extension (basically just a query wrapper, the queue lives on postgres proper), nice semantics, performance difference is negligible compared to rabbitmq, with wayyyyy less headaches

depends on the scenario. if i was getting to the point where the system isn't scaling off PG alone it would be the "good problem to have" stage and the time to migrate off to dedicated infra. A lot of projects get too complex in design too early and spend more on infra than they need before they've sufficiently had enough traction to justify the engineering effort.

Would you use a caching layer in front of PG or just scale up PG?