Dispatching in one application and processing in another one

[albertovaccarella]

This is more a question than an issue, based on what I understood from the source code (since I couldn't find it in the docs nor in the issues).

Am I right in understanding that this BullMQ wrapper is meant to dispatch and process jobs within the same Adonis application?

My use case is a common one in service oriented architecture, where one service would post something to the queue (e.g. "some data processing completed") and some other would pick it up to do something with it (e.g. "send email to notifiy users about new data being ready").

@RomainLanz would you suggest to use BullMQ directly in this case or am I missing something about this package that would cater to my use case?

[RomainLanz]

Currently, the package dispatches a job inside your Redis storage. Then, a worker (another process) will listen, read, and execute your job when it is free.

You will likely have one or multiple workers handling your jobs in production.