Global modules in NestJS - Performance & Optimization

Performance: Global modules

MEDIUM IMPACT

Global modules affect the initial load time and memory usage by making services available app-wide without repeated imports.

Sharing a service across multiple modules in a NestJS app

NestJS

import { Global, Module } from '@nestjs/common';

@Global()
@Module({
  providers: [SharedService],
  exports: [SharedService],
})
export class SharedModule {}

@Module({
  imports: [SharedModule],
})
export class AppModule {}

Declaring a module as global makes its providers available app-wide without repeated imports, reducing bundle size and initialization overhead.

📈 Performance GainSingle service instantiation and smaller initial bundle, improving startup speed.

Sharing a service across multiple modules in a NestJS app

NestJS

import { ModuleA } from './module-a';
import { ModuleB } from './module-b';
@Module({
  imports: [ModuleA, ModuleB],
})
export class AppModule {}

Repeatedly importing the same service in multiple modules causes redundant initialization and larger bundle size.

📉 Performance CostIncreases initial bundle size and triggers multiple service instantiations, blocking startup longer.

Performance Comparison

Pattern	Module Imports	Service Instantiations	Bundle Size Impact	Verdict
Repeated imports of shared services	Multiple	Multiple	Larger	[X] Bad
Global module with shared services	Single global import	Single	Smaller	[OK] Good

Rendering Pipeline

Global modules affect the server-side initialization phase before rendering, impacting how fast the app can start and serve content.

→Module Initialization

→Dependency Injection

→Server Response Preparation

⚠️ BottleneckModule Initialization due to repeated imports and service instantiations

Core Web Vital Affected

LCP

Global modules affect the initial load time and memory usage by making services available app-wide without repeated imports.

Optimization Tips

1Use @Global decorator to share services app-wide without repeated imports.

2Avoid making too many services global to prevent large bundle sizes and memory overhead.

3Monitor server startup time to detect performance issues from module initialization.

Performance Quiz - 3 Questions

What is the main performance benefit of using a global module in NestJS?

A It reduces repeated service instantiations across modules

B It automatically caches HTTP responses

C It decreases client-side rendering time

D It eliminates the need for dependency injection

DevTools: Network and Performance panels

How to check: Use Network panel to check initial bundle size and Performance panel to measure server response time and initialization duration.

What to look for: Look for smaller bundle sizes and shorter startup times when using global modules.

Practice

1. What is the main purpose of marking a module with @Global() in NestJS?

easy

A. To disable dependency injection for the module

B. To make its providers available across the entire application without importing the module repeatedly

C. To automatically register the module as a controller

D. To restrict the module's providers to only one feature module

Solution

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

   The @Global() decorator marks a module so its providers can be used app-wide without importing it in every module.

2. Step 2: Compare options with this behavior

   Only To make its providers available across the entire application without importing the module repeatedly correctly describes this behavior; others describe unrelated or incorrect effects.

3. Final Answer:

   To make its providers available across the entire application without importing the module repeatedly -> Option B

4. Quick Check:

   Global modules share providers app-wide [OK]

Hint: Global modules share providers app-wide without imports [OK]

Common Mistakes:

• Thinking @Global restricts providers to one module
• Confusing @Global with controller registration
• Assuming @Global disables dependency injection

2. Which of the following is the correct way to declare a global module in NestJS?

easy

A. @Global() @Module({ providers: [MyService], exports: [MyService] }) export class MyModule {}

B. @Module({ global: true, providers: [MyService], exports: [MyService] }) export class MyModule {}

C. @GlobalModule() @Module({ providers: [MyService] }) export class MyModule {}

D. @Module({ providers: [MyService], global: true }) export class MyModule {}

Solution

1. Step 1: Recall the correct decorator for global modules

   In NestJS, @Global() is used above the module class to mark it global.

2. Step 2: Check syntax correctness

   @Global() @Module({ providers: [MyService], exports: [MyService] }) export class MyModule {} correctly uses @Global() and @Module() with providers and exports arrays.

3. Final Answer:

   @Global() @Module({ providers: [MyService], exports: [MyService] }) export class MyModule {} -> Option A

4. Quick Check:

   Use @Global() decorator above @Module() [OK]

Hint: Use @Global() decorator above @Module() to declare global module [OK]

Common Mistakes:

• Using 'global: true' inside @Module() which is invalid
• Using non-existent @GlobalModule() decorator
• Forgetting to export providers in global module

3. Given this global module declaration:

@Global()
@Module({
  providers: [ConfigService],
  exports: [ConfigService],
})
export class ConfigModule {}

What happens if another module imports ConfigModule again?

medium

A. The application will throw a runtime error due to duplicate imports

B. The providers from ConfigModule are duplicated and cause errors

C. The providers are shared globally, so importing again has no effect

D. The ConfigModule providers become private to the importing module

Solution

1. Step 1: Understand global module behavior on imports

   Global modules share their providers app-wide, so importing them multiple times does not duplicate providers.

2. Step 2: Analyze the effect of importing a global module again

   Importing a global module again is harmless; providers remain shared and singleton.

3. Final Answer:

   The providers are shared globally, so importing again has no effect -> Option C

4. Quick Check:

   Global modules share providers; repeated imports don't duplicate [OK]

Hint: Global modules share providers; repeated imports don't duplicate [OK]

Common Mistakes:

• Assuming repeated imports cause errors
• Thinking providers become private on re-import
• Confusing global modules with normal modules

4. Consider this code snippet:

@Global()
@Module({
  providers: [LoggerService],
  exports: [LoggerService],
})
export class LoggerModule {}

But when you try to inject LoggerService in another module, you get an error: Nest can't resolve dependencies. What is the likely cause?

medium

A. You forgot to import LoggerModule in the root module

B. You did not mark LoggerModule with @Global()

C. You forgot to export LoggerService from LoggerModule

D. You did not add @Injectable() to LoggerService

Solution

1. Step 1: Check the module declaration

   The module is marked global and exports LoggerService, so imports and exports are correct.

2. Step 2: Verify LoggerService setup

   If LoggerService lacks @Injectable(), NestJS cannot inject it, causing the error.

3. Final Answer:

   You did not add @Injectable() to LoggerService -> Option D

4. Quick Check:

   Missing @Injectable() on service causes injection errors [OK]

Hint: Check if service has @Injectable() decorator [OK]

Common Mistakes:

• Assuming global modules don't need imports anywhere
• Forgetting to export providers
• Confusing missing @Global() with injection errors

5. You want to create a global module that provides a configuration service with environment variables. Which of the following is the best practice to ensure the service is singleton and accessible everywhere without repeated imports?

hard

A. Mark the module with @Global(), export the service, and import it only once in the root module

B. Mark the module with @Global(), export the service, and import the module in every feature module

C. Mark the module with @Global(), export the service, and do not import it anywhere else

D. Do not mark the module global; import it in every module that needs it

Solution

1. Step 1: Understand global module usage

   Global modules provide their exported providers app-wide without needing to import them repeatedly.

2. Step 2: Determine import requirements for global modules

   Global modules must be imported once, typically in the root module; after that, providers are available app-wide without further imports.

3. Final Answer:

   Mark the module with @Global(), export the service, and import it only once in the root module -> Option A

4. Quick Check:

   Import global modules once in root module [OK]

Hint: Global modules: mark @Global(), export, import once in root [OK]

Common Mistakes:

• Importing global modules in every feature module
• Not importing global modules at all
• Not marking the module as global