Why providers encapsulate business logic in NestJS - See It in Action

Why Providers Encapsulate Business Logic in NestJS

📖 Scenario: You are building a simple NestJS service to manage a list of books in a library. You want to keep the code clean and organized so that the logic for managing books is separate from the controller that handles HTTP requests.

🎯 Goal: Build a NestJS provider (service) that encapsulates the business logic for managing books, and use it in a controller to handle requests.

📋 What You'll Learn

Create a provider class called BooksService that holds the book data and methods

Add a configuration variable maxBooks to limit how many books can be added

Implement a method addBook in BooksService that adds a book only if the limit is not reached

Create a controller BooksController that uses BooksService to add and list books

💡 Why This Matters

🌍 Real World

In real apps, providers hold business rules like data validation, calculations, or database access, keeping controllers simple.

💼 Career

Understanding providers is key for backend developers using NestJS to build scalable, maintainable server applications.

1

Create the initial book data in the provider

Create a NestJS provider class called BooksService with a private array property books initialized to an empty array.

NestJS

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

@Injectable()
export class BooksService {
  // Your code here
}

Hint

Use private books: string[] = []; inside the class to hold the book list.

2

Add a configuration variable for maximum books

Inside the BooksService class, add a private readonly property called maxBooks and set it to 3.

NestJS

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

@Injectable()
export class BooksService {
  private books: string[] = [];
  // Your code here
}

Hint

Use private readonly maxBooks = 3; to set the limit.

3

Implement the addBook method with limit check

In the BooksService class, add a public method addBook that takes a title: string. It should add the title to books only if the current length is less than maxBooks. Return true if added, otherwise false.

NestJS

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

@Injectable()
export class BooksService {
  private books: string[] = [];
  private readonly maxBooks = 3;

  // Your code here
}

Hint

Check the length of this.books before adding the new title.

4

Create a controller that uses the provider

Create a NestJS controller class called BooksController that injects BooksService via the constructor. Add a method addNewBook that calls addBook on the service with a string 'NestJS Guide'.

NestJS

import { Injectable, Controller } from '@nestjs/common';
import { BooksService } from './books.service';

@Controller('books')
export class BooksController {
  constructor(private readonly booksService: BooksService) {}

  // Your code here
}

Hint

Inject BooksService in the constructor and call addBook inside addNewBook.

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