3 ms·
I have nothing against pg_boss[0] from the articel (I don't know anything about it), but there are plenty of queues and crons and schedulers for PG Some others
by zie 1y ago
I have nothing against pg_boss[0] from the articel (I don't know anything about it), but there are plenty of queues and crons and schedulers for PG
Some others:
* https://github.com/LaunchPlatform/bq https://github.com/LaunchPlatform/bq
* https://github.com/cybertec-postgresql/pg_timetable https://github.com/cybertec-postgresql/pg_timetable
* https://github.com/pgmq/pgmq https://github.com/pgmq/pgmq
* https://github.com/riverqueue/river https://github.com/riverqueue/river
* https://github.com/oban-bg/oban https://github.com/oban-bg/oban
* https://github.com/pgadmin-org/pgagent https://github.com/pgadmin-org/pgagent
* https://github.com/citusdata/pg_cron https://github.com/citusdata/pg_cron
etc. There are plenty of options to choose from.
0: https://github.com/timgit/pg-boss https://github.com/timgit/pg-boss
- TkTech 1y agoGonna toss my own hat in the ring there for the python+postgres ecosystem :) https://github.com/tktech/chancy https://github.com/tktech/chancy > As a rule of thumb, if you're processing less than 1000 jobs per day or your jobs are mostly lightweight operations (like sending emails or updating records), you can stick with this solution. This seems... excessively low? Chancy is on the heavier side and happily does many millions of jobs per day. Postgres has no issue with such low throughput, even on resource constrained systems (think a $5 vps). Maybe they meant 1000 per second?
- zie 1y agoI missed that. That does seem very small, 1k jobs/day is nothing. Chancy also looks pretty neat. Thanks for sharing!
- cpursley 1y agoAlso worth mentioning: https://www.pgflow.dev/ https://www.pgflow.dev/