CRUD operations with Prisma in NextJS - Performance & Optimization

Performance: CRUD operations with Prisma

MEDIUM IMPACT

This affects server response time and client perceived loading speed when performing database operations.

Fetching multiple related records in a single request

NextJS

const usersWithPosts = await prisma.user.findMany({ include: { posts: true } });

Fetches users and their posts in a single optimized query, reducing database round-trips.

📈 Performance Gainsingle query, reduces server blocking and speeds up response time

Fetching multiple related records in a single request

NextJS

const users = await prisma.user.findMany();
for (const user of users) {
  user.posts = await prisma.post.findMany({ where: { userId: user.id } });
}

This triggers one database query per user, causing many sequential queries and slow response.

📉 Performance Costblocks server response for N+1 queries, increasing latency linearly with number of users

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple sequential queries (N+1 problem)	0 (server-side)	0	0	[X] Bad
Single optimized query with include/select	0 (server-side)	0	0	[OK] Good

Rendering Pipeline

Prisma CRUD operations run on the server before sending data to the client. Slow queries delay server response, increasing LCP and blocking rendering.

→Server Processing

→Network Transfer

→Client Rendering

⚠️ BottleneckServer Processing due to inefficient or multiple database queries

Core Web Vital Affected

LCP

This affects server response time and client perceived loading speed when performing database operations.

Optimization Tips

1Avoid running Prisma queries inside loops to prevent N+1 query problems.

2Use Prisma's include and select to fetch related data in a single query.

3Minimize data fetched to only what is needed to reduce response size and speed up loading.

Performance Quiz - 3 Questions

What is the main performance issue with running multiple Prisma queries inside a loop to fetch related data?

A It causes many database round-trips, increasing server response time.

B It reduces the bundle size of the client code.

C It improves caching on the client side.

D It speeds up the rendering on the client.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by XHR/fetch, and observe the number and timing of API calls for data fetching.

What to look for: Look for multiple sequential API calls indicating N+1 queries or a single call with fast response time for optimized queries.

Practice

1. What does the prisma.user.create() method do in Next.js with Prisma?

easy

A. It adds a new user record to the database.

B. It fetches all user records from the database.

C. It updates an existing user record.

D. It deletes a user record from the database.

Solution

1. Step 1: Understand the method name

   The method create() is used to add new data in Prisma.

2. Step 2: Match method to CRUD operation

   Creating means adding new records, so prisma.user.create() adds a new user.

3. Final Answer:

   It adds a new user record to the database. -> Option A

4. Quick Check:

   Create method = Add new record [OK]

Hint: Create method adds new data, not read or delete [OK]

Common Mistakes:

• Confusing create() with findMany() which reads data
• Thinking create() updates existing records
• Assuming create() deletes records

2. Which of the following is the correct syntax to update a user with id 5 using Prisma in Next.js?

easy

A. prisma.user.edit({ where: { id: 5 }, data: { name: 'Alice' } })

B. prisma.user.modify({ id: 5, name: 'Alice' })

C. prisma.user.update({ where: { id: 5 }, data: { name: 'Alice' } })

D. prisma.user.change({ id: 5, data: { name: 'Alice' } })

Solution

1. Step 1: Identify Prisma update syntax

   Prisma uses update() with where and data keys to update records.

2. Step 2: Check option correctness

   Only prisma.user.update({ where: { id: 5 }, data: { name: 'Alice' } }) uses correct method update() and proper keys where and data.

3. Final Answer:

   prisma.user.update({ where: { id: 5 }, data: { name: 'Alice' } }) -> Option C

4. Quick Check:

   Update method uses where and data keys [OK]

Hint: Update uses update({ where, data }) syntax [OK]

Common Mistakes:

• Using non-existent methods like modify(), change(), edit()
• Missing where or data keys in update()
• Passing id directly without where object

3. Given this code snippet in Next.js with Prisma:

const users = await prisma.user.findMany({ where: { active: true } });
console.log(users.length);

What will console.log(users.length) output?

medium

A. Always 0, because findMany returns undefined.

B. The total number of users, active or not.

C. An error because findMany needs data key.

D. The number of active users in the database.

Solution

1. Step 1: Understand findMany with where filter

   The findMany() method returns an array of records matching the where condition.

2. Step 2: Analyze the filter condition

   Only users with active: true are returned, so users.length is count of active users.

3. Final Answer:

   The number of active users in the database. -> Option D

4. Quick Check:

   findMany with where returns filtered array [OK]

Hint: findMany returns array; length counts filtered records [OK]

Common Mistakes:

• Thinking findMany returns undefined or error
• Ignoring the where filter effect
• Assuming it returns all users without filter

4. Identify the error in this Prisma delete operation:

await prisma.user.delete({ id: 10 });

medium

A. Missing the 'where' key wrapping the id.

B. Using delete() instead of remove().

C. id should be a string, not a number.

D. delete() cannot be used with await.

Solution

1. Step 1: Check delete() method syntax

   Prisma's delete() requires an object with a where key specifying the record to delete.

2. Step 2: Identify missing where key

   The code passes { id: 10 } directly, missing where: { id: 10 }.

3. Final Answer:

   Missing the 'where' key wrapping the id. -> Option A

4. Quick Check:

   Delete needs where key with id [OK]

Hint: Delete needs where: { id } object, not just id [OK]

Common Mistakes:

• Omitting where key in delete()
• Using remove() which does not exist in Prisma
• Thinking id type must be string always
• Believing delete() can't be awaited

5. You want to update a user's email only if the user exists, otherwise create a new user with that email. Which Prisma method best fits this use case in Next.js?

hard

A. prisma.user.create({ data: { email } })

B. prisma.user.upsert({ where: { email }, update: { email }, create: { email } })

C. prisma.user.update({ where: { email }, data: { email } })

D. prisma.user.findUnique({ where: { email } })

Solution

1. Step 1: Understand the upsert method

   Upsert updates if record exists, else creates new one in Prisma.

2. Step 2: Match use case to method

   Since we want to update or create based on existence, upsert() fits perfectly.

3. Final Answer:

   prisma.user.upsert({ where: { email }, update: { email }, create: { email } }) -> Option B

4. Quick Check:

   Upsert = update or create [OK]

Hint: Use upsert to update or create in one call [OK]

Common Mistakes:

• Using update() alone which fails if user missing
• Using create() alone which fails if user exists
• Using findUnique() which only reads data