A sample repository showing how to run NestJS with Bull module, having a standalone worker process. This is useful when you need that the main process (which is scheduling the jobs based on API calls for example) is not interrupted by the queued jobs.
The advantage of this approach, as opposed to Separate (sandboxed/forked) processors is that you have the Dependency Injection (and IoC) container available within your processors, thanks to this running as a standalone application.
The downside is that you it will not utilize multi-core CPUs, as the worker process is running in a single thread. This is simple to work around by running multiple instances of the worker process, either by scaling the worker horizontally (e.g. running multiple instances of the worker in a Kubernetes cluster) or by running multiple instances of the worker process in a single machine (e.g. using PM2).
# Install dependencies
yarn install
# Run the main process
yarn start:dev
# Run the worker process in a separate terminal
yarn start:workerNow, make a GET request to http://localhost:3000/ and you should see the job being scheduled and processed by the worker process.
curl http://localhost:3000/