What is the configuration to use @taskforcesh/nestjs-bullmq-pro with a serverless valkey.

[horlaarsco]

I started using @taskforcesh/nestjs-bullmq-pro with AWS serverless valkey everything seems to work fine but it seems like bullMQ keeps the connection alive which is not so good for a serverless application.

For the picture above there have been no request or job added to the server in the last 12 hours but this just last 1 hour and it says there are currently 121 connections.

How can I close the connection when its not in use in nestjs.

Thanks.

[manast]

The way BullMQ is designed it requires the workers to have a permanent connection to Redis. If they did not have it then they will not be able to detect that new jobs are available in the queue. If you want to open and close connections manually you can do it but that is probably not going to be so efficient, using manual processing: https://docs.bullmq.io/patterns/manually-fetching-jobs

[horlaarsco]

So, it’s likely inefficient to use a serverless approach for managing BullMQ queues due to this issue. Additionally, it seems that the number of connections corresponds directly to the number of queues on the API.

[manast]

Unless you wrap the queue handling in something like https://github.com/taskforcesh/bullmq-proxy where the proxy will call your serverless function for every job to process then the answer is no. At the end of the day some service must act as a the queue consumer and this service needs to permanently monitor if new jobs are ready to be processed.