Move CPU-heavy work such as image processing, expensive crypto, or large transformations out of the HTTP event loop. Use `worker_threads` for CPU-bound local work, or enqueue a job to BullMQ/RabbitMQ when it should be retried and scaled independently. The request path should validate input, persist a job record, enqueue a job, and return a queued status. The worker performs the work and updates the record. Do not block the controller waiting for completion; make jobs idempotent and configure ...
Installs into .claude/skills of the current project.
Are you the author of Nestjs Performance?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-nestjs-performance-61be1d4f)
Move CPU-heavy work such as image processing, expensive crypto, or large transformations out of the HTTP event loop. Use `worker_threads` for CPU-bound local work, or enqueue a job to BullMQ/RabbitMQ when it should be retried and scaled independently.
The request path should validate input, persist a job record, enqueue a job, and return a queued status. The worker performs the work and updates the record. Do not block the controller waiting for completion; make jobs idempotent and configure retries/backoff and bounded retention.
