The N+1 Query Problem Every Developer Hits

The N+1 query problem is one of the most common performance bottlenecks in databases. It happens when an app runs one query for a list, then runs another query for each item.

Example

JS
// Fetch users, then fetch posts per user (bad)
const users = await db.users.findMany();
for (const user of users) {
  user.posts = await db.posts.findMany({ where: { userId: user.id } });
}
Copy

• If you have 100 users, that’s 101 queries. Disaster.

• Fix: Use Joins or Includes

JS
// Prisma ORM example
const users = await db.user.findMany({
  include: { posts: true }
});
Copy

This reduces 101 queries → 1 query.

Quick Checklist

✅ Look for loops making DB queries.

✅ Use joins/includes to batch queries.

✅ Profile DB calls in logs.

What To Do Next

Run a profiler in staging. If queries explode with more data, you’ve hit N+1. Fix it early.