cque VS Asynq

Noice! I am keen to give this a go.. the broker code are small and seems easy enough to implement for different backends.

having a quick glance, it does remind me a lot of que-go (https://github.com/bgentry/que-go) that is inspired by similar project written in ruby which use postgresql lock cleverly to take tasks from queue, work on it and release lock.

I liked the implementation so much and how easy it was to write worker for it, i ended up modifying it to use go channel (https://github.com/santrancisco/cque) as queue for worker task.. i used it in several personal projects over the years for cli tools that can leverage from having async tasks/jobs handle by workers.

EDIT : I think the best for my case will be to use the asynq library with a custom js client, it's quite easy to implement (Detailed here)

Asynq does this pretty nicely https://github.com/hibiken/asynq/wiki/Periodic-Tasks

Asynq looks promising. Never used it myself. https://github.com/hibiken/asynq

Never used it, but it appears to fit most of the criteria. https://github.com/hibiken/asynq

https://github.com/hibiken/asynq is pretty close

I tried it 2 months ago and it was not suitable for dynamic CRON job enqueue scheduling

My current best option is AsynQ (https://github.com/hibiken/asynq but it uses redid and not Postgres for the db

Hi, I'm starting a new project that involves distributing task on different (and possibly distributed) workers in Golang. So I'm looking for the best task queue library to use; for now the ones I like are the following (in no particular order): - asynq - machinery - taskq

Asynq might do what you need https://github.com/hibiken/asynq