kue
kue copied to clipboard
Automattic
Kue dead?
No commits since January, it appears no work being dong on other branches either. Dozens of unresolved issues with no comments. Outstanding critical pull requests (https://github.com/Automattic/kue/pull/1183).
Is this project dead?
As per Automaticc, the project is "not part of any of our current projects, and is not being actively maintained". See their tweet response
I have been very busy recent year and my kue backlog has not reached my top priorities. Active maintainers needed @fridgerator
@behrad maybe it is time to post an official header message in the Readme to look for active maintainers ? you've done an awesome job on Kue for all this years, thanks a lot for that. But I think it's probably time to move on if you can't maintain it anymore. Kue is a significant part of many peoples' node.js infrastructure and the fact that it's not maintained at the moment is creating lots of issues for node.js users. It used to be the most solid job queue solution and right now there is nothing basically ... (ok there is bull, but the way they handle the jobs concurrency and the queues is a bit of a no-go for me)
@didil could you please elaborate more about what is wrong with the way bull handles the concurrency and queues that makes it a no go for you?
@manast I want to be able to fine tune the concurrency level per job without creating one queue per job, I can do that with kue https://github.com/Automattic/kue#processing-concurrency . But I couldn't find a way to do that with bull https://github.com/OptimalBits/bull/blob/master/REFERENCE.md#queueprocess
the defined concurrency for each process function stacks up for the Queue
the line I quoted above is my biggest concern with bull. I understand it's just a design decision, but that behavior is not what I'm looking for most of the time when I'm building a web app
Can you create a PR for the updated README @didil I am also open to review code contributions 👍
@behrad I'm a little confused, it's your project right now, how would I know what you want to write exactly about handing it over to the next maintainer ?
@behrad Can you conclude the open TODO?
Let's take the next step in rebirthing Kue.
@manast to follow up on my comment above (and to be fair) I've been using bull in production for a few months now. works great. so if anybody is wondering what to do about this situation and can work with how bull handles queues and job concurrency, just switch to bull ...
@didil BTW. The behaviour you mentioned is no different in Bull in fact. Kue is just creating new queues (requiring extra connections) for every new type you add. So you can easily get the same behaviour with Bull...
you can also try Bull: https://github.com/OptimalBits/bull
Can I connect in bull in php?
