I am trying hard in all of my projects to simplify my code. Remove as many tools/services as possible and the tools that I do use, stick to simple ones that are easy to learn and maintain.
Bull is the job queue manager that I currently use. It's not a bad project, but it is more advanced and I feel like it's not lightweight. I like lightweight if I can help it.
I have found a couple of other projects: rsmq and bee-queue. I know bee-queue works with Arena UI and is popular. It's written in javascript, however.
Both of these projects have on their readme that one thing they like about themselves is that they (1) are powered by Redis and (2) are 1000 lines of code or smaller.
Currently, I am leaning towards rsmq because it boasts itself on being small and also states that you don't need a dedicated server to run jobs on. It runs on your existing app process. Bull can do this as well but after using it for a while I can see why splitting it off into it's own dedicated app can be beneficial.
I am trying hard in all of my projects to simplify my code. Remove as many tools/services as possible and the tools that I do use, stick to simple ones that are easy to learn and maintain.
Bull is the job queue manager that I currently use. It's not a bad project, but it is more advanced and I feel like it's not lightweight. I like lightweight if I can help it.
I have found a couple of other projects: rsmq and bee-queue. I know bee-queue works with Arena UI and is popular. It's written in javascript, however.
Both of these projects have on their readme that one thing they like about themselves is that they (1) are powered by Redis and (2) are 1000 lines of code or smaller.
Currently, I am leaning towards rsmq because it boasts itself on being small and also states that you don't need a dedicated server to run jobs on. It runs on your existing app process. Bull can do this as well but after using it for a while I can see why splitting it off into it's own dedicated app can be beneficial.