gue

Exciting time for distributed, transactional task queue projects built on the top of PostgreSQL! Here's the most heavily upvoted in the past 12 months Hatchet https://news.ycombinator.com/item?id=39643136 Inngest https://news.ycombinator.com/item?id=36403014 Windmill https://news.ycombinator.com/item?id=35920082 HN comments on Temporal.io https://github.com/temporalio https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... Internally we rant about the complexity of the above projects vs using transactional job queues libs like: river https://news.ycombinator.com/item?id=38349716 neoq: [https://github.com/acaloiaro/neoq](https://github.com/acaloi... gue: [https://github.com/vgarvardt/gue](https://github.com/vgarvar... Deep inside can't wait to see some like ThePrimeTimeagen to review it ;) https://www.youtube.com/@ThePrimeTimeage

How does this compare to https://github.com/vgarvardt/gue?

We are looking right now to use a stable PG job queue built in Go. We have found 2 already existing ones: * neoq: https://github.com/acaloiaro/neoq * gue: https://github.com/vgarvardt/gue Neoq is new and we found it to have some features (like scheduling tasks) that were attractive. The maintainer has also been responsive to fixing our bug reports and addressing our concerns as we try it out. Gue has been around for a while and is probably serving its users well. Looking forward to trying out River now. I do wonder if neoq and river might be better off joining forces.