Idea for job triggering? #1872
Replies: 2 comments
-
I think BullMQ can solve that use case already without any new features. Have you read this blog post? |
Beta Was this translation helpful? Give feedback.
-
Yes @manast, this one and others... I concluded that I need a more general-purpose "orchestrator" at a higher level. I had to implement a rudimentary one as I explained here: Current children-children-children... type chaining suggestion, without a conditional flow logic can only handle a small part of possible scenarios. Adding a simple orchestrator feature to BullMQ, would help to solve many cases. |
Beta Was this translation helpful? Give feedback.
-
FlowJobs have a top-down approach, you want a final result and you define children to reach that. I have a scenario that needs the reverse logic:
{ status: "updated"}
. In this case a chain of other events (a tree) should be triggered.For example (I'm dealing with datasets):
I had that implemented using bree using a list of job definitions and a JOB_CHAIN construct, but started to move to redis/bullmq for inter-microservice communication and caching. I was hoping o use Flows after an initial read, but it does not seem to fit.
As I'm pretty new to bullmq (2 days), any idea to approach the problem will be very much appreciated.
Edit: I missed that the repo has a Discussion section, please feel free to move this there. I also found the following related discussion:
Flow Producer Design for cases where children jobs are dynamically defined by another worker
Beta Was this translation helpful? Give feedback.
All reactions