We use pgmq with the pgmq-go client, and it has clients in many different languages, it's amazing.
The queues persist on disk and visualizations of queues can easily be made with grafana or just pure sql requests.
The fact that the queues lives in the same database as all the other data is also a huge benefit if the 5-15ms time penalty is not an issue.
At least until people - in a couple of years - figure out that the "Postgres for everything" fad was just as much of a bad idea as "MongoDB for everything" and "Put Redis into everything".
It's not "Postgres for everything", it's "Postgres by default". Nobody is saying you should replace your billion-message-per-second Kafka cluster (or whatever) with Postgres, but plenty of people are saying "don't start with a Kafka cluster when you have two messages a day", which is a much better idea than "MongoDB by default".
loafoe|1 month ago
cientifico|1 month ago
https://nanovms.com/dev/tutorials/running-postgres-as-a-unik...
cies|1 month ago
The MySQL + Redis + AWS' elasti-cron (or whatever) was a ghetto compared to Postgres.
saberd|1 month ago
this_user|1 month ago
stavros|1 month ago
dzonga|1 month ago
mysql less maintenance + more performant
pjmlp|1 month ago
Turns out it is a matter of feature set.
yawboakye|1 month ago