A narrow Next-owned health response
// app/api/web-status/route.ts
export function GET() {
return Response.json({ web: 'ok' });
}This is a web-adjacent response with no duplicate product domain logic.
Back to week 3
Topic
Use Route Handlers without replacing Nest
Definition
Route Handlers are Next.js request handlers defined in route.ts that can return HTTP responses for web-adjacent endpoints.
In simpler words
They handle narrow Next-owned HTTP work; they are not a second home for the product backend.
Keeping ownership clear prevents ticket rules, authentication, and validation from drifting across two servers.
After this you can
- Identify a valid Route Handler use
- Explain why tickets remain in Nest
- Return an HTTP response from route.ts
Choose the server that owns the concern
A Route Handler can serve a Next-specific integration edge, such as a web-only callback or a narrow adapter. It is defined beside the relevant app route and returns a standard HTTP response.
Nest already owns product REST endpoints, TypeORM persistence, cookie JWT guards, and domain rules. Duplicating those endpoints in app/api creates two implementations that can disagree.
Mistake: duplicating ticket CRUD in Next
// Wrong — app/api/tickets/route.ts reimplements ticket creation
export async function POST(request: Request) { /* validate + write tickets */ }
// Right — the browser calls the Nest tickets API through its established clientOne product resource needs one authoritative validation and authorization path.
Keep endpoint boundaries explicit
Definition
A handler’s location does not decide product ownership; the domain, authentication model, and consumers do.
In simpler words
Document why a Next handler exists so it does not become an accidental parallel API.
Validate and authenticate any handler according to its own threat model.
Avoid proxying an endpoint merely to conceal a missing API contract decision.
Live playground
Route Handlers playground
Classify each endpoint as Next-owned edge work or Nest product API work.
Nest: TypeORM, cookie JWT, domain rules.
Keep in mind
- Use route.ts only for a clear Next-owned HTTP concern.
- Keep product ticket endpoints in Nest.
- Return explicit status codes and response shapes from handlers.
Test
Check your understanding
At least 10 questions — mix of concept, syntax, practical, and logic. Score ≥ 80% (enforced by the API) to save progress.
Checking your session…
10 questions · concept 3 · syntax 2 · practical 3 · logic 2