What are route handlers vs API routes in App Router?
Assesses fundamental understanding of Next.js conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
In the App Router, API routes are now called "Route Handlers" and use the route.js file convention instead of the pages-based approach.
Pages Router (API Routes):
pages/api/users.js
App Router (Route Handlers):
app/api/users/route.js
jsx
// app/api/users/route.js
export async function GET(request) {
const users = await getUsers();
return Response.json(users);
}
export async function POST(request) {
const data = await request.json();
const user = await createUser(data);
return Response.json(user, { status: 201 });
}
export async function PUT(request) {
const data = await request.json();
const user = await updateUser(data);
return Response.json(user);
}
export async function DELETE(request) {
await deleteUser(request.nextUrl.searchParams.get("id"));
return new Response(null, { status: 204 });
}
Route handlers support all HTTP methods and provide better TypeScript support and Web APIs compatibility.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.