Why providers encapsulate business logic in NestJS

Introduction

Providers hold the main work of your app, like rules and tasks. They keep this work separate from how you show things or get data.

When you want to keep your app organized by separating tasks from display.

When you need to reuse the same logic in different parts of your app.

When you want to test your app's rules without worrying about the user interface.

When you want to easily change how your app works without changing how it looks.

When you want to share data or functions across different parts of your app.

Syntax

NestJS

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

@Injectable()
export class MyService {
  businessLogic() {
    // your logic here
  }
}

@Injectable() marks the class as a provider that NestJS can manage.

Providers are usually classes that contain methods with your app's main tasks.

Examples

A simple provider that adds two numbers.

NestJS

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

@Injectable()
export class MathService {
  add(a: number, b: number): number {
    return a + b;
  }
}

A provider that manages a list of users.

NestJS

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

@Injectable()
export class UserService {
  private users = [];

  addUser(user: any) {
    this.users.push(user);
  }

  getUsers() {
    return this.users;
  }
}

Sample Program

This provider holds the logic to create a greeting message. It keeps this logic separate from where it is used, like a controller.

NestJS

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

@Injectable()
export class GreetingService {
  getGreeting(name: string): string {
    return `Hello, ${name}! Welcome to NestJS.`;
  }
}

// Usage example (in a controller or another provider):
const greetingService = new GreetingService();
console.log(greetingService.getGreeting('Alice'));

Important Notes

Providers help keep your code clean and easy to manage.

They make testing easier because you can test logic without UI.

Always use @Injectable() to let NestJS know about your provider.

Summary

Providers hold the main tasks and rules of your app.

They keep logic separate from display and data access.

This makes your app easier to organize, test, and reuse.

Practice

1. Why do NestJS providers encapsulate business logic instead of placing it directly in controllers?

easy

A. To make the app run faster

B. Because controllers cannot contain any code

C. To keep the code organized and separate concerns

D. Because providers handle user interface rendering

Solution

1. Step 1: Understand roles of controllers and providers

   Controllers handle requests and responses, while providers hold the main business rules and logic.

2. Step 2: Recognize separation of concerns

   Separating logic into providers keeps code organized, easier to test, and reusable.

3. Final Answer:

   To keep the code organized and separate concerns -> Option C

4. Quick Check:

   Separation of concerns = A [OK]

Hint: Remember: providers = logic, controllers = routes [OK]

Common Mistakes:

• Thinking controllers should hold business logic
• Believing providers speed up app performance
• Confusing providers with UI rendering

2. Which of the following is the correct way to define a provider class in NestJS that encapsulates business logic?

easy

A. @Injectable() export class MyService { doTask() { return 'done'; } }

B. export class MyService { constructor() {} }

C. function MyService() { return 'done'; }

D. const MyService = () => 'done';

Solution

1. Step 1: Identify NestJS provider syntax

   Providers must be decorated with @Injectable() to be recognized by NestJS.

2. Step 2: Check class structure

   @Injectable() export class MyService { doTask() { return 'done'; } } shows a class with @Injectable() and a method, which is correct for a provider.

3. Final Answer:

   @Injectable() export class MyService { doTask() { return 'done'; } } -> Option A

4. Quick Check:

   @Injectable() + class = B [OK]

Hint: Look for @Injectable() decorator on classes [OK]

Common Mistakes:

• Omitting @Injectable() decorator
• Using plain functions instead of classes
• Not exporting the provider class

3. Given this provider code, what will be the output when appService.getGreeting() is called?

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

@Injectable()
export class AppService {
  getGreeting() {
    return 'Hello from provider!';
  }
}

medium

A. 'Hello from provider!'

B. undefined

C. Error: Method not found

D. 'Hello from controller!'

Solution

1. Step 1: Analyze the getGreeting method

   The method returns the string 'Hello from provider!'.

2. Step 2: Understand method call result

   Calling appService.getGreeting() returns the exact string defined.

3. Final Answer:

   'Hello from provider!' -> Option A

4. Quick Check:

   Method returns string = A [OK]

Hint: Method returns string literal, expect exact output [OK]

Common Mistakes:

• Confusing provider output with controller output
• Expecting undefined if method is not async
• Assuming error without checking method existence

4. Identify the error in this provider code snippet:

@Injectable()
export class UserService {
  getUser() {
    return this.user;
  }
}

medium

A. getUser method should be async

B. Missing declaration of 'user' property

C. Missing @Controller decorator

D. UserService should not be injectable

Solution

1. Step 1: Check class properties

   The method getUser returns this.user, but 'user' is not declared anywhere in the class.

2. Step 2: Understand consequences

   Accessing an undeclared property will cause runtime errors or undefined returns.

3. Final Answer:

   Missing declaration of 'user' property -> Option B

4. Quick Check:

   Undeclared property access = C [OK]

Hint: Check if all used properties are declared in the class [OK]

Common Mistakes:

• Thinking @Controller is needed on providers
• Assuming async needed without async code
• Believing providers can't be injectable

5. You want to reuse business logic for calculating discounts in multiple controllers. What is the best way to organize this in NestJS?

hard

A. Put the discount calculation code inside each controller separately

B. Use a global variable to store discount values accessible by all controllers

C. Write the discount logic directly in the main.ts bootstrap file

D. Create a provider service with discount logic and inject it where needed

Solution

1. Step 1: Identify code reuse best practice

   Duplicating logic in controllers causes maintenance issues and breaks separation of concerns.

2. Step 2: Use providers for shared logic

   Creating a provider service encapsulates the discount logic and allows injection into any controller.

3. Final Answer:

   Create a provider service with discount logic and inject it where needed -> Option D

4. Quick Check:

   Shared logic in providers = D [OK]

Hint: Use providers to share logic across controllers [OK]

Common Mistakes:

• Duplicating logic in controllers
• Using global variables instead of providers
• Placing logic in bootstrap file