Query builder in NestJS - Performance & Optimization

Performance: Query builder

MEDIUM IMPACT

Query builders affect server response time and data fetching speed, impacting how fast the page can load dynamic content.

Fetching user data with related posts

NestJS

const users = await this.userRepository.createQueryBuilder('user')
  .leftJoinAndSelect('user.posts', 'post')
  .getMany();

Single optimized query fetches users and their posts together, reducing database calls.

📈 Performance GainSingle query reduces database load and server response time significantly.

Fetching user data with related posts

NestJS

const users = await this.userRepository.find();
for (const user of users) {
  user.posts = await this.postRepository.find({ where: { userId: user.id } });
}

This triggers one query for users plus one query per user for posts, causing N+1 query problem.

📉 Performance CostTriggers N+1 database queries, increasing server response time linearly with user count.

Performance Comparison

Pattern	Database Queries	Server Processing	Network Payload	Verdict
N+1 Query Pattern	Multiple queries (1 + N)	High due to repeated queries	Larger due to multiple responses	[X] Bad
Optimized Query Builder	Single combined query	Low due to single query	Smaller and efficient	[OK] Good

Rendering Pipeline

Query builders run on the server before rendering. Efficient queries reduce server processing time and data transfer, speeding up the critical rendering path.

→Server Processing

→Network Transfer

→Client Rendering

⚠️ BottleneckServer Processing due to inefficient or multiple database queries

Core Web Vital Affected

LCP

Query builders affect server response time and data fetching speed, impacting how fast the page can load dynamic content.

Optimization Tips

1Avoid N+1 query patterns by using joins in query builders.

2Fetch all needed related data in a single query to reduce server load.

3Monitor API calls in DevTools to ensure minimal and fast queries.

Performance Quiz - 3 Questions

What is the main performance problem with the N+1 query pattern in query builders?

A It caches all data on the client side.

B It reduces the number of queries to one.

C It causes many database queries, increasing server response time.

D It compresses the network payload.

DevTools: Network

How to check: Open DevTools Network panel, filter XHR/fetch requests, observe number of API calls and their timing.

What to look for: Fewer API calls with faster response times indicate efficient query usage.