Handling Large Numbers of Dependent Jobs in BullMQ - Best Practices?

[jgalbsss]

I'm working with BullMQ in a Node.js application and need advice on handling job dependencies at scale. Here's my scenario:
I have a parent job that needs to spawn multiple child jobs (potentially up to 3000)
The parent job needs to wait for all child jobs to complete before proceeding
Need a solution that can handle this volume of dependent jobs reliably
What's the recommended pattern for handling large numbers of dependent jobs while:
Avoiding event listener limits
Maintaining good performance
Ensuring reliable job completion tracking
Has anyone solved this at scale? Looking for battle-tested approaches or best practices.