How to Detect and Fix N+1 Queries in Node.js The Complete Guide

N+1 queries silently kill your API performance. Learn what causes them, how to detect them manually, and how to auto-detect them with one line of middleware. What is the N+1 Query Problem? The N+1 query problem is one of the most common performance killers in web APIs. It happens when your code executes 1 query to fetch a list of items, then N additional queries to fetch related data for each item. Example: You want to show 50 orders with their product names. // ❌ BAD: N+1 — 51 queries total app . get ( ' /api/orders ' , async ( req , res ) => { const orders = await db . query ( ' SELECT * FROM orders LIMIT 50 ' ); // 1 query for ( const order of orders ) { order . product = await db . query ( // 50 queries ' SELECT name FROM products WHERE id = $1 ' , [ order . product_id ] ); } res . json ( orders ); }); This makes 51 database queries instead of 2. At 50 orders it's slow. At 500 orders, your API is dead. Why N+1 Queries Are So Dangerous The scary part? You won't notice them during de