Prisma setup in NestJS - Performance & Optimization

Performance: Prisma setup in NestJS

MEDIUM IMPACT

This affects server response time and API data fetching speed, impacting how fast the frontend receives data.

Setting up Prisma client in NestJS for database access

NestJS

import { PrismaClient } from '@prisma/client';
import { Injectable, OnModuleDestroy, OnModuleInit } from '@nestjs/common';

@Injectable()
export class PrismaService extends PrismaClient implements OnModuleInit, OnModuleDestroy {
  async onModuleInit() {
    await this.$connect();
  }

  async onModuleDestroy() {
    await this.$disconnect();
  }
}

@Injectable()
export class UserService {
  constructor(private prisma: PrismaService) {}

  async getUsers() {
    return await this.prisma.user.findMany();
  }
}

Using a singleton PrismaService injected via NestJS DI avoids multiple connections and manages lifecycle properly.

📈 Performance GainSingle DB connection reused, reducing latency and memory overhead

Setting up Prisma client in NestJS for database access

NestJS

import { Injectable } from '@nestjs/common';
import { PrismaClient } from '@prisma/client';

@Injectable()
export class UserService {
  private prisma = new PrismaClient();

  async getUsers() {
    return await this.prisma.user.findMany();
  }
}

Creating a new PrismaClient instance directly in the service causes multiple connections and higher memory use.

📉 Performance CostAdds multiple DB connections, increasing latency and memory usage per request

Performance Comparison

Pattern	DB Connections	Memory Usage	Response Latency	Verdict
Direct PrismaClient in service	Multiple per service instance	High	Higher due to connection overhead	[X] Bad
Singleton PrismaService with DI	Single shared connection	Low	Lower due to reuse	[OK] Good

Rendering Pipeline

Prisma setup affects backend API response time, which influences frontend rendering speed indirectly by controlling data availability.

→Server Processing

→Network Transfer

→Frontend Rendering

⚠️ BottleneckServer Processing (database query execution and connection management)

Core Web Vital Affected

INP

This affects server response time and API data fetching speed, impacting how fast the frontend receives data.

Optimization Tips

1Always use a singleton PrismaService injected via NestJS DI to avoid multiple DB connections.

2Connect and disconnect PrismaClient in lifecycle hooks to manage resources efficiently.

3Monitor API response times in DevTools Network tab to catch Prisma-related delays early.

Performance Quiz - 3 Questions

What is the main performance issue with creating a new PrismaClient instance inside each NestJS service?

A It blocks CSS from loading

B It causes frontend rendering delays directly

C It creates multiple database connections increasing latency and memory use

D It increases bundle size significantly

DevTools: Network

How to check: Open DevTools Network tab, make API requests, and observe response times for data fetching endpoints.

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

Practice

1. What is the main purpose of PrismaService in a NestJS application?

easy

A. To provide a reusable database client instance for querying the database

B. To handle HTTP requests and responses

C. To define the database schema

D. To manage application configuration settings

Solution

1. Step 1: Understand PrismaService role

   PrismaService wraps the Prisma Client to provide a single database connection instance across the app.

2. Step 2: Differentiate from other roles

   It does not handle HTTP or define schema; those are handled by controllers and Prisma schema files respectively.

3. Final Answer:

   To provide a reusable database client instance for querying the database -> Option A

4. Quick Check:

   PrismaService = database client provider [OK]

Hint: PrismaService is your database helper in NestJS [OK]

Common Mistakes:

• Confusing PrismaService with controllers
• Thinking PrismaService defines schema
• Assuming PrismaService manages config

2. Which of the following is the correct way to import and provide PrismaService in a NestJS module?

easy

A. import { PrismaService } from '@nestjs/common';

@Module({ controllers: [PrismaService] })

B. import { PrismaService } from './prisma.service';

@Module({ providers: [PrismaService], exports: [PrismaService] })

C. import PrismaService from 'prisma';

@Module({ providers: [PrismaService] })

D. import { PrismaService } from './prisma.service';

@Module({ imports: [PrismaService] })

Solution

1. Step 1: Check import source

   PrismaService is a custom service, so it must be imported from its local file, not from '@nestjs/common' or external packages.

2. Step 2: Verify module metadata

   It should be listed under providers and exports to be injectable and reusable in other modules.

3. Final Answer:

   import { PrismaService } from './prisma.service'; @Module({ providers: [PrismaService], exports: [PrismaService] }) -> Option B

4. Quick Check:

   Local import + providers and exports = correct setup [OK]

Hint: PrismaService is a provider, import locally and add to providers [OK]

Common Mistakes:

• Importing PrismaService from wrong package
• Adding PrismaService to controllers instead of providers
• Using imports array instead of providers

3. Given this PrismaService method in NestJS, what will console.log(user) output if the user with ID 1 exists?

async getUserById(id: number) {
  return this.prisma.user.findUnique({ where: { id } });
}

const user = await prismaService.getUserById(1);
console.log(user);

medium

A. A syntax error because findUnique is not a function

B. An array of all users in the database

C. An object containing the user's data with ID 1

D. null, because findUnique returns nothing

Solution

1. Step 1: Understand findUnique behavior

   findUnique returns a single record matching the unique filter or null if none found.

2. Step 2: Given user with ID 1 exists

   The method returns the user object with ID 1, so console.log prints that object.

3. Final Answer:

   An object containing the user's data with ID 1 -> Option C

4. Quick Check:

   findUnique returns single object or null [OK]

Hint: findUnique returns one object or null, not array [OK]

Common Mistakes:

• Thinking findUnique returns an array
• Assuming it always returns null
• Confusing findUnique with findMany

4. You wrote this PrismaService method but get a runtime error: Cannot read property 'user' of undefined. What is the likely cause?

async getAllUsers() {
  return this.prisma.user.findMany();
}

Options:

medium

A. The Prisma Client instance was not initialized in PrismaService

B. The user model is missing in the Prisma schema

C. The method should be static to access prisma

D. findMany() requires parameters and cannot be empty

Solution

1. Step 1: Analyze error message

   'Cannot read property user of undefined' means this.prisma is undefined in the service.

2. Step 2: Check PrismaService initialization

   Prisma Client must be instantiated and assigned to this.prisma in the constructor; missing this causes the error.

3. Final Answer:

   The Prisma Client instance was not initialized in PrismaService -> Option A

4. Quick Check:

   Uninitialized prisma client = undefined error [OK]

Hint: Initialize prisma client in constructor to avoid undefined errors [OK]

Common Mistakes:

• Forgetting to instantiate PrismaClient in PrismaService
• Assuming findMany needs parameters
• Thinking method must be static

5. You want to create a NestJS service method that fetches all posts with their authors using Prisma. Which code snippet correctly uses Prisma to fetch posts including author data?

hard

A. return this.prisma.post.findMany({ where: { author: true } });

B. return this.prisma.post.findMany({ select: { authorId: true } });

C. return this.prisma.post.findUnique({ where: { id: 1 }, include: { author: true } });

D. return this.prisma.post.findMany({ include: { author: true } });

Solution

1. Step 1: Understand fetching related data

   To get posts with their authors, use findMany with include: { author: true } to load related author data.

2. Step 2: Check other options

   return this.prisma.post.findMany({ select: { authorId: true } }); only selects authorId, not author object. return this.prisma.post.findUnique({ where: { id: 1 }, include: { author: true } }); fetches one post, not all. return this.prisma.post.findMany({ where: { author: true } }); uses invalid where clause.

3. Final Answer:

   return this.prisma.post.findMany({ include: { author: true } }); -> Option D

4. Quick Check:

   Include loads related models in findMany [OK]

Hint: Use include to fetch related models in Prisma queries [OK]

Common Mistakes:

• Using select instead of include for relations
• Using findUnique when multiple records needed
• Incorrect where clause for relations