Why NestJS exists - Performance Evidence

Performance: Why NestJS exists

MEDIUM IMPACT

NestJS affects server-side application structure impacting development speed and maintainability, indirectly influencing server response times and scalability.

Building a scalable and maintainable Node.js backend application

NestJS

import { Controller, Get } from '@nestjs/common';
import { UsersService } from './users.service';

@Controller('users')
export class UsersController {
  constructor(private readonly usersService: UsersService) {}

  @Get()
  getUsers() {
    return this.usersService.findAll();
  }
}

Separates concerns with controllers and services, improving code clarity, maintainability, and easier scaling.

📈 Performance GainFaster development and easier optimization lead to more reliable and scalable server responses

Building a scalable and maintainable Node.js backend application

NestJS

const express = require('express');
const app = express();
app.get('/users', (req, res) => {
  // all logic in one place
  res.send('User list');
});
app.listen(3000);

Putting all logic in one place leads to messy code that is hard to maintain and scale, causing slower development and potential bugs.

📉 Performance CostIncreases development time and risk of inefficient code causing slower server responses under load

Performance Comparison

Pattern	Code Organization	Maintainability	Server Response Impact	Verdict
Monolithic Express app with inline logic	Poor	Low	Potentially slower under load	[X] Bad
NestJS with controllers and services	Excellent	High	Optimized and scalable	[OK] Good

Rendering Pipeline

NestJS structures backend code into modules, controllers, and services, which improves code organization and maintainability but does not directly affect browser rendering.

→Server Processing

→API Response Time

⚠️ BottleneckUnorganized code can cause slower server response times due to inefficient logic and harder debugging.

Optimization Tips

1Use NestJS to organize backend code for better maintainability and scalability.

2Better backend structure helps keep server response times low under load.

3NestJS improves developer productivity, indirectly benefiting user experience.

Performance Quiz - 3 Questions

How does using NestJS affect backend server performance?

A Directly speeds up browser rendering

B Improves code organization leading to easier optimization and scalability

C Increases bundle size on the client side

D Reduces CSS paint times

DevTools: Network

How to check: Open DevTools, go to Network tab, make requests to your backend API, and observe response times.

What to look for: Look for consistent and low response times indicating efficient backend processing.

Practice

1. Why was NestJS created as a framework for backend development?

easy

A. To replace frontend frameworks like React and Angular

B. To create mobile applications easily

C. To only support legacy JavaScript without TypeScript

D. To provide a clear and organized way to build scalable server-side apps

Solution

1. Step 1: Understand NestJS purpose

   NestJS is designed to help developers build backend applications that are easy to maintain and scale.

2. Step 2: Compare options with NestJS goals

   Options A, C, and D do not match NestJS's backend focus or modern language support.

3. Final Answer:

   To provide a clear and organized way to build scalable server-side apps -> Option D

4. Quick Check:

   Backend clarity and scalability = B [OK]

Hint: NestJS focuses on backend clarity and scalability [OK]

Common Mistakes:

• Confusing NestJS with frontend frameworks
• Thinking NestJS only supports old JavaScript
• Assuming NestJS is for mobile apps

2. Which of the following is the correct way to create a basic NestJS controller?

easy

A. import { Controller, Get } from '@nestjs/common';

@Controller('cats')
export class CatsController {
@Get()
findAll() {
return 'This action returns all cats';
}
}

B. import { Controller } from 'nestjs';

@Controller('/cats')
class Cats {
getAll() {
return 'Cats list';
}
}

C. const controller = require('nestjs').Controller;

controller('/cats', () => {
return 'Cats';
});

D. import { Controller, Post } from '@nestjs/common';

@Controller('cats')
export class CatsController {
findAll() {
return 'All cats';
}
}

Solution

1. Step 1: Check import and decorator usage

   import { Controller, Get } from '@nestjs/common'; @Controller('cats') export class CatsController { @Get() findAll() { return 'This action returns all cats'; } } correctly imports from '@nestjs/common' and uses @Controller and @Get decorators properly.

2. Step 2: Verify method and return value

   import { Controller, Get } from '@nestjs/common'; @Controller('cats') export class CatsController { @Get() findAll() { return 'This action returns all cats'; } }'s method findAll returns a string as expected for a GET route. Other options have wrong imports, missing decorators, or wrong HTTP method.

3. Final Answer:

   Option A code snippet -> Option A

4. Quick Check:

   Correct decorators and imports = A [OK]

Hint: Look for @Controller and @Get from '@nestjs/common' [OK]

Common Mistakes:

• Using wrong import paths
• Missing HTTP method decorators
• Using require instead of import

3. Consider this NestJS service code:

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

@Injectable()
export class MathService {
  double(value: number): number {
    return value * 2;
  }
}

const service = new MathService();
console.log(service.double(5));

What will be printed in the console?

medium

A. 10

B. 5

C. undefined

D. Error: Injectable decorator missing

Solution

1. Step 1: Understand the double method

   The method multiplies the input value by 2, so double(5) returns 10.

2. Step 2: Check usage of Injectable decorator

   The @Injectable decorator marks the class for NestJS dependency injection but does not affect direct instantiation or method output.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   5 times 2 equals 10 [OK]

Hint: Method doubles input; decorator doesn't block direct use [OK]

Common Mistakes:

• Thinking @Injectable prevents direct instantiation
• Expecting undefined return
• Confusing decorator effects with runtime errors

4. This NestJS controller code has an error:

import { Controller, Get } from '@nestjs/common';

@Controller('dogs')
export class DogsController {
  @Get()
  getDogs() {
    return this.dogs;
  }
}

What is the main problem here?

medium

A. The import statement is wrong

B. The controller is missing a constructor to initialize 'dogs'

C. The @Get decorator is used incorrectly

D. The method getDogs should be async

Solution

1. Step 1: Identify usage of 'this.dogs'

   The method returns 'this.dogs' but the class does not define or initialize 'dogs'.

2. Step 2: Check for initialization

   Without a constructor or property assignment, 'this.dogs' is undefined, causing runtime errors.

3. Final Answer:

   The controller is missing a constructor to initialize 'dogs' -> Option B

4. Quick Check:

   Undefined property needs initialization [OK]

Hint: Check if all used properties are initialized [OK]

Common Mistakes:

• Assuming decorators fix property issues
• Thinking async is required without async code
• Ignoring missing property initialization

5. You want to build a scalable backend app using NestJS that handles many users and keeps code organized. Which feature of NestJS helps most with this goal?

hard

A. Its use of global variables for shared state

B. Its built-in support for frontend UI components

C. Its modular architecture allowing separation of features into modules

D. Its automatic generation of mobile app code

Solution

1. Step 1: Identify scalability needs

   Scalable apps need clear separation of concerns and organized code structure.

2. Step 2: Match NestJS features to needs

   NestJS modules let you group related code, making it easier to maintain and scale. Other options do not support backend scalability.

3. Final Answer:

   Its modular architecture allowing separation of features into modules -> Option C

4. Quick Check:

   Modular design = scalable backend [OK]

Hint: Modular design is key for scalable backend apps [OK]

Common Mistakes:

• Confusing backend with frontend features
• Thinking NestJS generates mobile code
• Using global variables instead of modules