Prisma Query Shape, N+1, and Overfetching
Prisma performance depends more on query shape than on whether code lives in a repository. Repository Pattern improves organization, but it does not automatically produce efficient SQL.
N assignee/project many database round 1 Task list query loop over N Tasks queries trips → → →
// Prefer one intentional query shape when the UI needs related data. const tasks = await prisma.task.findMany({ where, select: { id: true, title: true, status: true, priority: true, assignee: { select: { id: true, displayName: true }, }, }, take: query.pageSize, });
Repository review questions • Does a list endpoint execute one bounded query shape or one query per row?
• Are we selecting large unused columns/relations?
• Are count and data queries both required for this screen?
• Does authorization scoping force expensive relation traversal that deserves an index?
• Is the same lookup repeated inside one request and safe to reuse?
Prisma currently recommends one reusable PrismaClient per process because multiple clients create multiple pools. It also explicitly calls out N+1 as a common query-performance problem. Production caution: Do not hide N+1 behind Promise.all. Concurrent N+1 is still N+1 and may put even more pressure on the connection pool.
Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.
Restate the goal of “Prisma Query Shape NPlusOne and Overfetching” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Before/after performance report with measured bottleneck, change, and regression guard.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const tasks = await prisma.task.findMany({
where: { workspaceId },
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: 20,
});Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.
Read the generated SQL before applying it and compare the change against existing production-shaped data.
Without copying the final source, create a second small scenario that applies “Prisma Query Shape NPlusOne and Overfetching” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Reduce N+1 or redundant requests before adding caches.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Optimizing from intuition only
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.