Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FlowProducer and when to use them? #1516

Closed
doebi opened this issue Nov 3, 2022 · 0 comments
Closed

FlowProducer and when to use them? #1516

doebi opened this issue Nov 3, 2022 · 0 comments

Comments

@doebi
Copy link

doebi commented Nov 3, 2022

I am trying to find an adequate solution to implementing following process in BullMQ.

* acquire information A
* process information from A to B
  - publish B to message broker
  - store B in DBMS 1
* process information from B to C
  - publish C to message broker
  - store C in DBMS 2

I read about FlowProducer and initally thought they might be a good fit. But from what I saw they are good at having multiple children jobs aggregated in one parent job which processes their output. So in my case If I map all the steps in a flow I would need multiple parent jobs, which is not possible.

My next idea is to create a Flow with steps [acquire, process, process] and have them add jobs to separate queues for DBMS 1, DBMS 2 and message broker. But in that case, do I still need the FlowProducer?

What are your thoughts?

@taskforcesh taskforcesh locked and limited conversation to collaborators Nov 3, 2022
@manast manast converted this issue into discussion #1517 Nov 3, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant