Constructor injection in NestJS - Performance & Optimization

Performance: Constructor injection

MEDIUM IMPACT

Constructor injection affects the initialization speed of services and components during app startup, impacting the time to first meaningful paint.

Injecting dependencies into a service or controller

NestJS

import { Injectable } from '@nestjs/common';
import { SomeDependency } from './some-dependency';

@Injectable()
export class MyService {
  constructor(private readonly dependency: SomeDependency) {}
}

Dependencies are injected automatically at construction, enabling faster and synchronous initialization.

📈 Performance GainReduces runtime lookup overhead; improves startup speed and lowers LCP.

Injecting dependencies into a service or controller

NestJS

import { Injectable, Injector } from '@nestjs/common';
import { SomeDependency } from './some-dependency';

@Injectable()
export class MyService {
  private dependency: SomeDependency;
  constructor(private injector: Injector) {}

  async init() {
    this.dependency = this.injector.get(SomeDependency);
  }
}

Using the Injector service to get dependencies at runtime delays initialization and adds overhead.

📉 Performance CostBlocks app startup until dependencies are resolved; triggers multiple runtime lookups increasing initialization time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual Injector.get() calls	0 (no DOM impact)	0	Blocks script execution delaying paint	[X] Bad
Constructor injection	0 (no DOM impact)	0	Non-blocking synchronous init, faster paint	[OK] Good

Rendering Pipeline

Constructor injection happens during the app's bootstrap phase before rendering. It ensures all dependencies are ready synchronously, so the app can render main content faster.

→App Initialization

→Script Execution

→First Contentful Paint

⚠️ BottleneckRuntime dependency resolution when using manual injector calls

Core Web Vital Affected

LCP

Constructor injection affects the initialization speed of services and components during app startup, impacting the time to first meaningful paint.

Optimization Tips

1Always prefer constructor injection over manual Injector.get() calls for dependencies.

2Constructor injection reduces runtime overhead and speeds up app initialization.

3Faster initialization improves Largest Contentful Paint (LCP) metric.

Performance Quiz - 3 Questions

What is the main performance benefit of constructor injection in NestJS?

A It allows lazy loading of dependencies to improve initial load time.

B It delays dependency resolution until first use, saving memory.

C Dependencies are resolved synchronously at startup, reducing runtime overhead.

D It reduces the size of the final JavaScript bundle.

DevTools: Performance

How to check: Record a startup profile and look for long scripting tasks during app bootstrap.

What to look for: Long blocking tasks caused by runtime dependency resolution indicate bad pattern; shorter startup scripting time indicates good constructor injection.