Entity definition in NestJS - Performance & Optimization

Performance: Entity definition

MEDIUM IMPACT

Entity definitions affect the initial database schema creation and runtime ORM operations, impacting server response time and query efficiency.

Defining a database entity with relations in NestJS using TypeORM

NestJS

import { Entity, PrimaryGeneratedColumn, Column, OneToMany } from 'typeorm';

@Entity()
export class User {
  @PrimaryGeneratedColumn()
  id: number;

  @Column()
  name: string;

  @OneToMany(() => Post, post => post.user, { lazy: true })
  posts: Promise<Post[]>;
}

Lazy loading defers loading related posts until explicitly requested, reducing initial query size and response time.

📈 Performance GainReduces initial query size and memory usage, improving response time by 50-100ms depending on data size.

Defining a database entity with relations in NestJS using TypeORM

NestJS

import { Entity, PrimaryGeneratedColumn, Column, OneToMany } from 'typeorm';

@Entity()
export class User {
  @PrimaryGeneratedColumn()
  id: number;

  @Column()
  name: string;

  @OneToMany(() => Post, post => post.user, { eager: true })
  posts: Post[];
}

Using eager loading on a OneToMany relation causes all related posts to load every time a user is fetched, increasing query time and memory usage.

📉 Performance CostTriggers large JOIN queries and loads unnecessary data, increasing response time by 100ms+ on large datasets.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Eager loading large relations in entity	N/A (server-side)	N/A	N/A	[X] Bad
Lazy loading relations on demand	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Entity definitions influence how ORM generates SQL queries and fetches data, affecting server-side processing before sending data to the client.

→Query Generation

→Database Fetch

→Data Serialization

⚠️ BottleneckDatabase Fetch due to inefficient queries or eager loading of large relations.

Optimization Tips

1Avoid eager loading large or deep relations in entity definitions.

2Use lazy loading to fetch related data only when necessary.

3Select only required fields in queries to reduce data size.

Performance Quiz - 3 Questions

What is a performance downside of using eager loading in NestJS entity relations?

A It delays loading related data until explicitly requested.

B It reduces database query size by selecting fewer fields.

C It loads all related data even if not needed, increasing response time.

D It caches data on the client to improve speed.

DevTools: Network

How to check: Open DevTools Network tab, inspect API responses for payload size and response time when fetching entities.

What to look for: Look for large JSON payloads or slow response times indicating heavy or inefficient entity loading.