Event handling in NestJS - Performance & Optimization

Performance: Event handling

MEDIUM IMPACT

Event handling affects how quickly the server responds to incoming events or requests, impacting API responsiveness and CPU usage.

Handling multiple events with many listeners

NestJS

import { Injectable } from '@nestjs/common';
import { EventEmitter2 } from 'eventemitter2';

@Injectable()
export class AppService {
  constructor(private eventEmitter: EventEmitter2) {}

  registerListener() {
    this.eventEmitter.on('dataEvent', () => {
      // optimized single handler for all data
    });
  }
}

Uses a single listener to handle all events, reducing CPU overhead and speeding up event dispatch.

📈 Performance GainSingle function call per event, lowering CPU usage and improving responsiveness.

Handling multiple events with many listeners

NestJS

import { Injectable } from '@nestjs/common';
import { EventEmitter2 } from 'eventemitter2';

@Injectable()
export class AppService {
  constructor(private eventEmitter: EventEmitter2) {}

  registerListeners() {
    for (let i = 0; i < 1000; i++) {
      this.eventEmitter.on('dataEvent', () => {
        // heavy processing
      });
    }
  }
}

Registers 1000 listeners for the same event, causing high CPU usage and slow event dispatch.

📉 Performance CostTriggers 1000 function calls per event, increasing CPU load and delaying event handling.

Performance Comparison

Pattern	Event Listeners	CPU Overhead	Impact	Verdict
Many heavy event listeners	1000+	Very High	High CPU usage delays request processing	[X] Bad
Single optimized event listener	1	Low	Minimal CPU usage, fast event processing	[OK] Good

Rendering Pipeline

Event handling in NestJS triggers JavaScript functions in response to events, affecting the main thread's (event loop) ability to process incoming requests and other tasks.

→JavaScript Execution

→Event Loop

⚠️ BottleneckJavaScript Execution when many or heavy event handlers run synchronously

Core Web Vital Affected

N/A

Event handling affects how quickly the server responds to incoming events or requests, impacting API responsiveness and CPU usage.

Optimization Tips

1Avoid registering many listeners for the same event to reduce CPU load.

2Keep event handlers lightweight and asynchronous when possible.

3Use DevTools Performance panel (with Node --inspect) to identify slow event handlers.

Performance Quiz - 3 Questions

What is a performance risk of registering many event listeners for the same event in NestJS?

A It reduces memory usage significantly.

B It causes many function calls per event, increasing CPU load.

C It speeds up event dispatch automatically.

D It prevents events from firing.

DevTools: Performance (Chrome DevTools with Node --inspect)

How to check: Run `node --inspect` on your NestJS app, connect chrome://inspect, record a performance profile while triggering events; look for long tasks or many function calls related to event handlers.

What to look for: High CPU time spent in event handler functions indicates poor performance; fewer and shorter tasks indicate good handling.

Practice

1. What is the main purpose of event handling in a NestJS application?

easy

A. To allow different parts of the app to react to actions without being tightly connected

B. To directly call methods from other classes

C. To replace all HTTP requests with events

D. To store data permanently in the database

Solution

1. Step 1: Understand event handling concept

   Event handling lets parts of an app respond to actions independently, avoiding tight coupling.

2. Step 2: Compare options

   Only To allow different parts of the app to react to actions without being tightly connected describes this purpose correctly; others describe unrelated concepts.

3. Final Answer:

   To allow different parts of the app to react to actions without being tightly connected -> Option A

4. Quick Check:

   Event handling = loose coupling reaction [OK]

Hint: Event handling means reacting without tight connections [OK]

Common Mistakes:

• Thinking event handling replaces HTTP requests
• Confusing event handling with direct method calls
• Assuming event handling stores data

2. Which decorator is used to mark a class as an event handler in NestJS?

easy

A. @HandleEvent

B. @EventListener

C. @EventsHandler

D. @EventSubscriber

Solution

1. Step 1: Recall NestJS event handler syntax

   The correct decorator to mark event handler classes is @EventsHandler.

2. Step 2: Verify options

   Options B, C, and D are not valid NestJS decorators for event handlers.

3. Final Answer:

   @EventsHandler -> Option C

4. Quick Check:

   @EventsHandler marks event handlers [OK]

Hint: Use @EventsHandler to mark event handler classes [OK]

Common Mistakes:

• Using @EventListener which is not a NestJS decorator
• Confusing with @HandleEvent which does not exist
• Using @EventSubscriber which is from other frameworks

3. Given this event handler code, what will be logged when eventBus.publish(new UserCreatedEvent('Alice')) is called?

import { EventsHandler, IEventHandler } from '@nestjs/cqrs';

export class UserCreatedEvent {
  constructor(public readonly username: string) {}
}

@EventsHandler(UserCreatedEvent)
export class UserCreatedHandler implements IEventHandler<UserCreatedEvent> {
  handle(event: UserCreatedEvent) {
    console.log(`User created: ${event.username}`);
  }
}

medium

A. User created: undefined

B. No output because eventBus.publish does nothing

C. Error: handle method missing

D. User created: Alice

Solution

1. Step 1: Understand event publishing and handling

   Publishing UserCreatedEvent triggers UserCreatedHandler which logs the username.

2. Step 2: Check the handle method output

   The handle method logs "User created: " plus the event's username, which is "Alice".

3. Final Answer:

   User created: Alice -> Option D

4. Quick Check:

   Event publish triggers handler log [OK]

Hint: Publishing event triggers handle() logging username [OK]

Common Mistakes:

• Assuming username is undefined
• Thinking handle method is missing
• Believing eventBus.publish does nothing

4. What is wrong with this event handler code?

import { EventsHandler, IEventHandler } from '@nestjs/cqrs';

export class OrderPlacedEvent {
  constructor(public readonly orderId: number) {}
}

@EventsHandler(OrderPlacedEvent)
export class OrderPlacedHandler implements IEventHandler<OrderPlacedEvent> {
  handle() {
    console.log('Order placed:', orderId);
  }
}

medium

A. The handle method is missing the event parameter

B. The @EventsHandler decorator is used incorrectly

C. The event class should not have a constructor

D. The console.log syntax is invalid

Solution

1. Step 1: Check handle method signature

   The handle method must accept the event parameter to access event data.

2. Step 2: Identify usage of event data

   Inside handle, orderId is used but not defined because event parameter is missing.

3. Final Answer:

   The handle method is missing the event parameter -> Option A

4. Quick Check:

   handle(event) needs event parameter [OK]

Hint: handle() must receive event parameter to access data [OK]

Common Mistakes:

• Omitting event parameter in handle method
• Misusing @EventsHandler decorator
• Thinking constructor is not needed in event class

5. You want to handle two different events, UserCreatedEvent and UserDeletedEvent, in one handler class. Which approach correctly implements this in NestJS?

hard

A. Use @EventsHandler without parameters and check event type inside handle method

B. Use @EventsHandler(UserCreatedEvent, UserDeletedEvent) on one class and implement handle(event) with type checks

C. Use @EventsHandler on one class but implement two separate handle methods named handleUserCreated and handleUserDeleted

D. Create two separate handler classes each with @EventsHandler for one event

Solution

1. Step 1: Understand multiple event handling in one class

   In NestJS, you can pass multiple event classes to @EventsHandler decorator on one class.

2. Step 2: Implement single handle method with event type checks

   The handle method receives any event instance; inside it, you check the event type to handle accordingly.

3. Final Answer:

   Use @EventsHandler(UserCreatedEvent, UserDeletedEvent) on one class and implement handle(event) with type checks -> Option B

4. Quick Check:

   Multiple events in one handler use @EventsHandler(...events) [OK]

Hint: Use @EventsHandler with multiple events and one handle method [OK]

Common Mistakes:

• Trying to define multiple handle methods in one class
• Creating separate classes instead of one combined handler
• Using @EventsHandler without parameters