Queue consumers (processors) in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a queue processor using NestJS.

NestJS

import { Processor, [1] } from '@nestjs/bull';

@Processor('email')
export class EmailProcessor {
  // processor methods here
}

Drag options to blanks, or click blank then click option'

AProcess

BInjectQueue

COnQueueCompleted

DQueue

Attempts:

3 left

💡 Hint

Common Mistakes

Using @InjectQueue instead of @Process

Confusing @OnQueueCompleted with @Process

The @Processor decorator is used with the Process decorator to define queue processors in NestJS Bull.

2fill in blank

medium

Complete the code to define a method that processes jobs in the queue.

NestJS

@Process('send_email')
async [1](job: Job) {
  // processing logic
}

Drag options to blanks, or click blank then click option'

AhandleJob

BsendEmail

CprocessJob

DonCompleted

Attempts:

3 left

💡 Hint

Common Mistakes

Using lifecycle event names like onCompleted as method name

Using unrelated method names

The method name can be anything, but processJob clearly indicates it processes the job.

3fill in blank

hard

Fix the error in the processor method signature to correctly receive the job data.

NestJS

async processJob([1]: Job) {
  console.log(job.data);
}

Drag options to blanks, or click blank then click option'

Adata

Bjob

Cpayload

Dtask

Attempts:

3 left

💡 Hint

Common Mistakes

Naming the parameter data and trying to access job.data

Using unrelated parameter names

The parameter must be named job to access job.data.

4fill in blank

hard

Fill both blanks to import and use the Job type from Bull in the processor.

NestJS

import { Processor, Process } from '@nestjs/bull';
import { [1] } from 'bull';

@Processor('notifications')
export class NotificationProcessor {
  @Process('notify')
  async handleNotification(job: [2]) {
    // handle notification
  }
}

Drag options to blanks, or click blank then click option'

AJob

BQueue

CJobOptions

DWorker

Attempts:

3 left

💡 Hint

Common Mistakes

Importing or using incorrect types like Queue or Worker

Not typing the job parameter

The Job type from Bull is imported and used to type the job parameter.

5fill in blank

hard

Fill all three blanks to create a processor that logs job data and marks completion.

NestJS

import { Processor, Process, OnQueueCompleted } from '@nestjs/bull';
import { Job } from 'bull';

@Processor('tasks')
export class TaskProcessor {
  @Process('execute')
  async [1](job: [2]) {
    console.log(job.data);
  }

  @OnQueueCompleted()
  async [3](job: Job) {
    console.log(`Job completed: ${job.id}`);
  }
}

Drag options to blanks, or click blank then click option'

AhandleExecute

BJob

ConComplete

DQueue

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong types for job parameter

Incorrect method names for processing or completion

The processor method is named handleExecute, the job parameter is typed Job, and the completion handler is onComplete.

Practice

1. What is the main purpose of a queue consumer (processor) in a NestJS application?

easy

A. To send HTTP requests to external APIs

B. To render UI components on the client side

C. To listen to a queue and process jobs asynchronously in the background

D. To manage database migrations synchronously

Solution

1. Step 1: Understand the role of queue consumers

   Queue consumers listen to queues and handle jobs asynchronously, allowing background processing.

2. Step 2: Compare with other options

   Sending HTTP requests, rendering UI, and managing migrations are unrelated to queue consumers.

3. Final Answer:

   To listen to a queue and process jobs asynchronously in the background -> Option C

4. Quick Check:

   Queue consumer = background job handler [OK]

Hint: Queue consumers handle background jobs, not UI or HTTP [OK]

Common Mistakes:

• Confusing queue consumers with HTTP controllers
• Thinking queue consumers run synchronously
• Assuming queue consumers manage UI rendering

2. Which decorator is used to mark a class as a queue consumer (processor) in NestJS?

easy

A. @Processor

B. @Queue

C. @Process

D. @Consumer

Solution

1. Step 1: Identify the decorator for queue consumers

   The @Processor decorator marks a class as a queue consumer in NestJS.

2. Step 2: Differentiate from other decorators

   @Process marks methods, @Queue and @Consumer are not valid NestJS decorators for this purpose.

3. Final Answer:

   @Processor -> Option A

4. Quick Check:

   Class decorator for consumers = @Processor [OK]

Hint: Class decorator for consumers is @Processor, method decorator is @Process [OK]

Common Mistakes:

• Using @Process on the class instead of methods
• Confusing @Processor with @Queue
• Assuming @Consumer is a valid decorator

3. Given the following NestJS queue consumer code, what will be logged when a job with data { name: 'Alice' } is processed?

import { Processor, Process } from '@nestjs/bull';
import { Job } from 'bull';

@Processor('email')
export class EmailProcessor {
  @Process('send')
  async handleSend(job: Job) {
    console.log(`Sending email to ${job.data.name}`);
  }
}

medium

A. No output because handleSend is not called

B. Sending email to Alice

C. Error: job.data is not defined

D. Sending email to undefined

Solution

1. Step 1: Understand job data usage

   The job object contains data with a name property 'Alice'. The method logs this value.

2. Step 2: Confirm method is called on 'send' jobs

   The @Process('send') decorator ensures handleSend runs for jobs named 'send' in the 'email' queue.

3. Final Answer:

   Sending email to Alice -> Option B

4. Quick Check:

   job.data.name = 'Alice' logged correctly [OK]

Hint: Job data is accessed via job.data inside @Process methods [OK]

Common Mistakes:

• Assuming job.data is undefined
• Thinking method won't run without explicit call
• Confusing queue name with job name

4. Identify the error in this NestJS queue consumer code snippet:

import { Processor, Process } from '@nestjs/bull';
import { Job } from 'bull';

@Processor('notifications')
export class NotificationProcessor {
  @Process()
  async handleNotification(job: Job) {
    console.log('Notification:', job.data.message);
  }
}

medium

A. Job parameter type should be any, not Job

B. The class should not have @Processor decorator

C. Console.log syntax is incorrect

D. @Process decorator is missing the job name argument

Solution

1. Step 1: Check @Process decorator usage

   @Process requires a job name string to specify which jobs to handle; it's missing here.

2. Step 2: Validate other parts

   @Processor on class is correct, Job type is valid, console.log syntax is correct.

3. Final Answer:

   @Process decorator is missing the job name argument -> Option D

4. Quick Check:

   @Process needs job name argument [OK]

Hint: @Process must specify job name string inside parentheses [OK]

Common Mistakes:

• Omitting job name in @Process decorator
• Removing @Processor from class
• Changing Job type unnecessarily

5. You want to create a NestJS queue consumer that processes two different job types: 'email' and 'sms' in the same queue 'notifications'. Which is the correct way to define the processor class and methods?

hard

A. Use @Processor('notifications') on class, and two methods with @Process('email') and @Process('sms') decorators

B. Use two separate classes each with @Processor('notifications') and one @Process method

C. Use @Processor('email') and @Processor('sms') on the same class with one @Process method

D. Use @Process('notifications') on methods without @Processor on class

Solution

1. Step 1: Understand queue and job type separation

   The queue is 'notifications'. The job types are 'email' and 'sms'. One class can handle multiple job types with separate @Process decorators.

2. Step 2: Validate correct decorator usage

   @Processor('notifications') marks the queue. Methods use @Process('email') and @Process('sms') to handle each job type.

3. Final Answer:

   Use @Processor('notifications') on class, and two methods with @Process('email') and @Process('sms') decorators -> Option A

4. Quick Check:

   One class, multiple @Process methods for job types [OK]

Hint: One @Processor class can have many @Process methods for different jobs [OK]

Common Mistakes:

• Creating multiple classes for same queue unnecessarily
• Using multiple @Processor decorators on one class
• Omitting @Processor on class and only using @Process