Why API routes serve backend logic in NextJS - Performance Evidence

Performance: Why API routes serve backend logic

MEDIUM IMPACT

API routes affect server response time and client load speed by handling backend logic separately from frontend rendering.

Handling backend logic in a Next.js app

NextJS

export async function GET() {
  // API route handles backend logic server-side
  const data = await fetchDataFromDB();
  return new Response(JSON.stringify({ message: data }), { status: 200 });
}

export default async function Page() {
  // Fetch data server-side during rendering
  const res = await fetch('http://localhost:3000/api/data');
  const data = await res.json();
  return <div>{data.message}</div>;
}

Backend logic runs on server, so client receives ready data, reducing render blocking and improving LCP and INP.

📈 Performance GainReduces client blocking by 200-500ms, improves LCP and interaction speed

Handling backend logic in a Next.js app

NextJS

export default function Page() {
  // Fetch data directly inside the component using client-side fetch
  const [data, setData] = React.useState(null);
  React.useEffect(() => {
    fetch('/api/data').then(res => res.json()).then(setData);
  }, []);
  return <div>{data ? data.message : 'Loading...'}</div>;
}

Fetching backend data on the client delays rendering and increases time to interactive, causing slower LCP and INP.

📉 Performance CostBlocks rendering until data fetch completes, increasing LCP by 200-500ms depending on network

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Client-side data fetching	Low	1+ (due to delayed content)	High (delayed paint)	[X] Bad
Server-side API routes	Low	1 (initial render)	Low (fast paint)	[OK] Good

Rendering Pipeline

API routes run backend logic on the server before sending data to the client, reducing client-side rendering delays.

→Server Processing

→Network Transfer

→Client Rendering

⚠️ BottleneckClient Rendering when backend logic is done client-side

Core Web Vital Affected

LCP

API routes affect server response time and client load speed by handling backend logic separately from frontend rendering.

Optimization Tips

1Run backend logic in API routes to reduce client-side blocking.

2Avoid fetching backend data only on the client to improve LCP.

3Use server-side data fetching to deliver ready content faster.

Performance Quiz - 3 Questions

How do API routes in Next.js improve page load performance?

A By bundling backend code with frontend code to reduce requests

B By running all logic on the client to reduce server load

C By running backend logic on the server before sending data to the client

D By delaying data fetching until after page load

DevTools: Performance

How to check: Record a page load and look for long tasks or delays in the Main thread caused by client-side data fetching.

What to look for: Look for delayed Largest Contentful Paint (LCP) and long scripting times indicating client blocking.

Practice

1. Why do Next.js API routes serve backend logic in a Next.js project?

easy

A. They are used only to style the frontend components.

B. They replace the need for React components in the app.

C. They allow running server-side code like data fetching and secure operations within the same project.

D. They automatically generate static HTML pages.

Solution

1. Step 1: Understand the role of API routes

   API routes in Next.js let you write backend code inside your project to handle tasks like fetching data or processing forms.

2. Step 2: Identify what backend logic means

   Backend logic means code that runs on the server, such as secure operations or database access, which API routes enable.

3. Final Answer:

   They allow running server-side code like data fetching and secure operations within the same project. -> Option C

4. Quick Check:

   API routes = backend logic handler [OK]

Hint: API routes run server code inside Next.js projects [OK]

Common Mistakes:

• Thinking API routes style frontend
• Confusing API routes with React components
• Believing API routes generate static pages

2. Which of the following is the correct way to define a Next.js API route handler?

easy

A. const handler = () => Hello

B. function handler() { return Hello }

C. export function handler() { console.log('Hello') }

D. export default function handler(req, res) { res.status(200).json({ message: 'Hello' }) }

Solution

1. Step 1: Recognize API route syntax

   Next.js API routes export a default function that receives req and res to handle requests and responses.

2. Step 2: Check each option

   export default function handler(req, res) { res.status(200).json({ message: 'Hello' }) } correctly exports a default function with req and res and sends a JSON response. Others either lack export default or return JSX, which is incorrect for API routes.

3. Final Answer:

   export default function handler(req, res) { res.status(200).json({ message: 'Hello' }) } -> Option D

4. Quick Check:

   API route = export default function(req, res) [OK]

Hint: API routes export default function with req, res [OK]

Common Mistakes:

• Returning JSX instead of JSON
• Not exporting default function
• Missing req and res parameters

3. Given this Next.js API route code, what will be the JSON response when a GET request is made?

export default function handler(req, res) {
  if (req.method === 'GET') {
    res.status(200).json({ success: true, data: 'Hello World' })
  } else {
    res.status(405).json({ error: 'Method Not Allowed' })
  }
}

medium

A. {"error":"Method Not Allowed"}

B. {"success":true,"data":"Hello World"}

C. An HTML page with 'Hello World'

D. A runtime error occurs

Solution

1. Step 1: Check request method handling

   The handler checks if the request method is 'GET'. If yes, it sends a 200 status with JSON containing success and data.

2. Step 2: Determine response for GET request

   Since the request is GET, the response will be JSON: {"success":true,"data":"Hello World"} with status 200.

3. Final Answer:

   {"success":true,"data":"Hello World"} -> Option B

4. Quick Check:

   GET request returns success JSON [OK]

Hint: GET method returns success JSON, others error [OK]

Common Mistakes:

• Assuming all methods return success
• Expecting HTML instead of JSON
• Confusing status codes

4. Identify the error in this Next.js API route code:

export default function handler(req, res) {
  if (req.method === 'POST') {
    res.json({ message: 'Data received' })
  } else {
    res.status(405).json({ error: 'Method Not Allowed' })
  }
}

medium

A. No error, code is correct

B. Using res.json instead of res.send

C. Missing status code in the POST response

D. Missing req parameter

Solution

1. Step 1: Review response methods

   In Next.js API routes, res.json() sends a JSON response with a default status code of 200, which is correct and functional.

2. Step 2: Check each option

   The code properly handles POST with res.json() (200 OK implied) and other methods with 405 error. There are no syntax errors, runtime issues, or missing parameters. res.json is the right method for JSON responses.

3. Final Answer:

   No error, code is correct -> Option A

4. Quick Check:

   res.json defaults to 200, code runs correctly [OK]

Hint: res.json() defaults to status 200 [OK]

Common Mistakes:

• Thinking missing explicit status code is an error
• Confusing res.json and res.send
• Forgetting req or res parameters

5. You want to create a Next.js API route that securely processes a form submission only if the request method is POST and the request body contains a non-empty 'email' field. Which code snippet correctly implements this logic?

hard

A. export default function handler(req, res) {
if (req.method === 'POST' && req.body.email) {
res.status(200).json({ message: `Email ${req.body.email} received` })
} else {
res.status(400).json({ error: 'Invalid request' })
}
}

B. export default function handler(req, res) {
if (req.method === 'GET' || !req.body.email) {
res.status(200).json({ message: 'Form processed' })
} else {
res.status(400).json({ error: 'Invalid request' })
}
}

C. export default function handler(req, res) {
if (req.method === 'POST') {
res.status(200).json({ message: 'Form processed' })
} else {
res.status(400).json({ error: 'Invalid request' })
}
}

D. export default function handler(req, res) {
res.status(200).json({ message: 'Form processed' })
}

Solution

1. Step 1: Check method and body content

   The handler must verify the request method is POST and that the 'email' field exists and is not empty in the request body.

2. Step 2: Validate each option

   export default function handler(req, res) { if (req.method === 'POST' && req.body.email) { res.status(200).json({ message: `Email ${req.body.email} received` }) } else { res.status(400).json({ error: 'Invalid request' }) } } correctly checks both conditions and returns a success message with the email. Others either check wrong methods, ignore the email field, or always respond without validation.

3. Final Answer:

   export default function handler(req, res) { if (req.method === 'POST' && req.body.email) { res.status(200).json({ message: `Email ${req.body.email} received` }) } else { res.status(400).json({ error: 'Invalid request' }) } } -> Option A

4. Quick Check:

   POST + email check = export default function handler(req, res) { if (req.method === 'POST' && req.body.email) { res.status(200).json({ message: `Email ${req.body.email} received` }) } else { res.status(400).json({ error: 'Invalid request' }) } } [OK]

Hint: Check method and required fields before responding [OK]

Common Mistakes:

• Not checking request method
• Ignoring required fields in body
• Always returning success without validation