Injectable decorator in NestJS - Performance & Optimization

Performance: Injectable decorator

MEDIUM IMPACT

This affects the dependency injection system's initialization and service instantiation speed, impacting app startup and runtime responsiveness.

Managing service dependencies in a NestJS application

NestJS

@Injectable()
class UserRepository {}

@Injectable()
class UserService {
  constructor(private readonly repo: UserRepository) {}
}

NestJS injects and reuses singleton instances, reducing redundant object creation and improving startup speed.

📈 Performance GainSingle instantiation per service; faster startup and lower memory use.

Managing service dependencies in a NestJS application

NestJS

class UserService {
  constructor() {
    this.repo = new UserRepository();
  }
}

class UserRepository {}

Manually creating dependencies causes tight coupling and repeated instantiation, increasing startup time and memory use.

📉 Performance CostBlocks app startup longer due to manual object creation; no reuse of instances.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual new calls for dependencies	N/A	N/A	N/A	[X] Bad
Using @Injectable with DI container	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

The @Injectable decorator marks classes for NestJS's dependency injection container, which resolves and instantiates dependencies before app runtime.

→Initialization

→Dependency Resolution

→Service Instantiation

⚠️ BottleneckDependency Resolution stage can slow startup if many manual instantiations occur.

Core Web Vital Affected

INP

This affects the dependency injection system's initialization and service instantiation speed, impacting app startup and runtime responsiveness.

Optimization Tips

1Always use @Injectable to let NestJS manage service lifecycles efficiently.

2Avoid manual new calls for dependencies to reduce startup blocking.

3Reuse singleton instances to save memory and improve runtime speed.

Performance Quiz - 3 Questions

How does using @Injectable improve NestJS app performance?

A It enables efficient reuse of service instances, reducing startup time.

B It delays service instantiation until first use, increasing startup time.

C It forces manual creation of dependencies, increasing memory use.

D It disables dependency injection, improving runtime speed.

DevTools: Performance

How to check: Record app startup and look for long scripting tasks related to service instantiation.

What to look for: Long blocking times during initialization indicate manual instantiation overhead.

Practice

1. What is the main purpose of the @Injectable() decorator in NestJS?

easy

A. To style components with CSS

B. To define a route handler in a controller

C. To create a database connection automatically

D. To mark a class so NestJS can manage it for dependency injection

Solution

1. Step 1: Understand the role of @Injectable()

   This decorator tells NestJS that the class can be injected as a dependency, making it reusable and manageable by the framework.

2. Step 2: Differentiate from other decorators

   Other decorators like @Controller() or database decorators serve different purposes, not dependency injection.

3. Final Answer:

   To mark a class so NestJS can manage it for dependency injection -> Option D

4. Quick Check:

   @Injectable() = marks class for DI [OK]

Hint: Remember: @Injectable() means NestJS manages the class [OK]

Common Mistakes:

• Confusing @Injectable() with @Controller()
• Thinking it creates routes or database connections
• Assuming it styles components

2. Which of the following is the correct syntax to make a service class injectable in NestJS?

easy

A. function Injectable() { return class MyService {} }

B. class MyService {}

C. @Injectable() class MyService {}

D. @Injectable class MyService {}

Solution

1. Step 1: Recall correct decorator syntax

   In NestJS, decorators are functions called with parentheses, so @Injectable() is correct.

2. Step 2: Check each option

   class MyService {} lacks the decorator. function Injectable() { return class MyService {} } is invalid syntax. @Injectable class MyService {} misses parentheses after @Injectable.

3. Final Answer:

   @Injectable() class MyService {} -> Option C

4. Quick Check:

   Decorator syntax requires parentheses () [OK]

Hint: Always use parentheses with decorators like @Injectable() [OK]

Common Mistakes:

• Omitting parentheses after @Injectable
• Trying to use @Injectable without decorator syntax
• Confusing class and function syntax

3. Given the following code, what will be the output when appService.getMessage() is called?

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

@Injectable()
class AppService {
  getMessage() {
    return 'Hello from AppService';
  }
}

const appService = new AppService();
console.log(appService.getMessage());

medium

A. Hello from AppService

B. undefined

C. Error: AppService is not injectable

D. null

Solution

1. Step 1: Understand @Injectable() effect on class instantiation

   The @Injectable() decorator marks the class for NestJS DI but does not change normal instantiation behavior.

2. Step 2: Analyze the code execution

   The code creates an instance manually and calls getMessage(), which returns the string as expected.

3. Final Answer:

   Hello from AppService -> Option A

4. Quick Check:

   Manual instantiation still works; method returns string [OK]

Hint: Manual new works; decorator doesn't block normal class use [OK]

Common Mistakes:

• Assuming decorator breaks manual instantiation
• Expecting an error without NestJS container
• Thinking method returns undefined

4. Identify the error in this NestJS service code:

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

@Injectable
export class UserService {
  getUser() {
    return 'User data';
  }
}

medium

A. Missing parentheses after @Injectable decorator

B. Class name should be lowercase

C. Method getUser must be async

D. Missing export keyword

Solution

1. Step 1: Check decorator syntax

   The @Injectable decorator must be called with parentheses: @Injectable().

2. Step 2: Verify other code parts

   Class name casing is correct by convention. Method need not be async. Export keyword is present.

3. Final Answer:

   Missing parentheses after @Injectable decorator -> Option A

4. Quick Check:

   Decorator requires () to work properly [OK]

Hint: Always add () after decorators like @Injectable() [OK]

Common Mistakes:

• Forgetting parentheses after decorator
• Thinking method must be async
• Confusing export keyword presence

5. You want to create a reusable logging service in NestJS that other services can inject. Which of the following is the best way to define it?

hard

A. Create a class without @Injectable() and instantiate it manually everywhere

B. Use @Injectable() on the logging class and inject it where needed

C. Define logging functions in a plain JavaScript object and export it

D. Use @Controller() decorator on the logging class

Solution

1. Step 1: Understand dependency injection benefits

   Using @Injectable() allows NestJS to manage the logging service lifecycle and inject it automatically where needed.

2. Step 2: Evaluate options for reusability and testability

   Manual instantiation loses DI benefits. Plain objects lack lifecycle and DI. @Controller() is for routing, not services.

3. Final Answer:

   Use @Injectable() on the logging class and inject it where needed -> Option B

4. Quick Check:

   Injectable services = reusable and testable [OK]

Hint: Always use @Injectable() for reusable NestJS services [OK]

Common Mistakes:

• Skipping @Injectable() and instantiating manually
• Using @Controller() for services
• Using plain objects without DI benefits