API routes vs server actions decision in NextJS - Performance Comparison

Performance: API routes vs server actions decision

MEDIUM IMPACT

This affects server response time and client-side rendering speed by choosing how backend logic is executed and data is fetched.

Fetching data or performing server logic in Next.js app

NextJS

export async function serverAction() {
  const data = await fetchFromDatabase();
  return data;
}

// Called directly from server components or client with server action support

Server actions run server logic directly without extra HTTP requests, reducing latency and speeding up rendering.

📈 Performance GainEliminates extra network request, reducing LCP by 100-200ms and improving time to interactive

Fetching data or performing server logic in Next.js app

NextJS

export async function GET(request) {
  // API route handler
  const data = await fetchFromDatabase();
  return new Response(JSON.stringify(data));
}

// Client fetches data via fetch('/api/data')

API routes add an extra HTTP request and response cycle, increasing latency and delaying rendering.

📉 Performance CostAdds 1 extra network request, blocking rendering until response arrives, increasing LCP by 100-200ms

Performance Comparison

Pattern	Network Requests	Server Processing	Client Wait Time	Verdict
API Routes	1 extra HTTP request	Separate server handler	Client waits for response	[X] Bad
Server Actions	No extra HTTP request	Inline server logic	Minimal client wait	[OK] Good

Rendering Pipeline

API routes require a client request to the server, which triggers server processing, response serialization, then client parsing before rendering. Server actions run server code during rendering, skipping the client fetch step.

→Server Processing

→Network Request

→Client Rendering

⚠️ BottleneckNetwork Request latency and client waiting for response

Core Web Vital Affected

LCP

This affects server response time and client-side rendering speed by choosing how backend logic is executed and data is fetched.

Optimization Tips

1Avoid extra HTTP requests to reduce latency and improve LCP.

2Use server actions to run server logic inline during rendering.

3Check Network panel to verify number of requests and their timing.

Performance Quiz - 3 Questions

What is a main performance drawback of using API routes instead of server actions in Next.js?

A Extra network request adds latency

B Server actions increase bundle size

C API routes block client rendering permanently

D Server actions cause layout shifts

DevTools: Network

How to check: Open DevTools, go to Network tab, load page and observe number of requests and their timing

What to look for: Extra API route requests increase load time; server actions show fewer requests and faster content load

Practice

1. What is the main difference between Next.js API routes and server actions?

easy

A. API routes and server actions are exactly the same in Next.js.

B. API routes run only on the client; server actions run only on the server.

C. API routes create separate endpoints; server actions call server code directly from components.

D. API routes are used for styling; server actions handle routing.

Solution

1. Step 1: Understand API routes purpose

   API routes create separate API endpoints that the client can call to communicate with the server.

2. Step 2: Understand server actions purpose

   Server actions allow calling server code directly from React components without creating separate endpoints.

3. Final Answer:

   API routes create separate endpoints; server actions call server code directly from components. -> Option C

4. Quick Check:

   API routes vs server actions difference = D [OK]

Hint: API routes = endpoints; server actions = direct calls [OK]

Common Mistakes:

• Thinking API routes run on client side
• Confusing server actions with styling or routing
• Believing API routes and server actions are identical

2. Which of the following is the correct way to define a server action in Next.js?

easy

A. export default function handler(req, res) { /* server code */ }

B. export async function actionName() { /* server code */ }

C. function actionName() { return Server Action }

D. const actionName = () => fetch('/api/data')

Solution

1. Step 1: Identify server action syntax

   Server actions are defined as exported async functions that run on the server.

2. Step 2: Compare with API route syntax

   API routes use a default export function with (req, res) parameters, not named async functions.

3. Final Answer:

   export async function actionName() { /* server code */ } -> Option B

4. Quick Check:

   Server action syntax = B [OK]

Hint: Server actions use named async functions exported directly [OK]

Common Mistakes:

• Using default export with req, res (API route style)
• Writing server actions as React components
• Calling fetch inside server action definition

3. Given this Next.js server action code, what will be the output when called from a component?

export async function addNumbers(a, b) {
  return a + b;
}

medium

A. Returns a Promise resolving to the sum of a and b.

B. Returns undefined because server actions cannot return values.

C. Throws a syntax error due to missing parameters.

D. Returns a string concatenation of a and b.

Solution

1. Step 1: Analyze the server action function

   The function is async and returns the sum of a and b, which is a number.

2. Step 2: Understand async function return

   Async functions return a Promise that resolves to the returned value, here the sum.

3. Final Answer:

   Returns a Promise resolving to the sum of a and b. -> Option A

4. Quick Check:

   Async function returns Promise with sum = A [OK]

Hint: Async server actions return Promises with results [OK]

Common Mistakes:

• Thinking server actions cannot return values
• Confusing number addition with string concatenation
• Assuming syntax error due to parameters

4. You wrote this API route in Next.js but it throws an error:

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

What is the error and how to fix it?

medium

A. Response method json is invalid; use send instead.

B. Should use server action syntax instead of API route syntax.

C. Function must not be async in API routes.

D. Missing default export; change to export default async function handler(req, res).

Solution

1. Step 1: Identify API route export requirement

   API routes require a default export function to handle requests.

2. Step 2: Fix export statement

   Change named export to default export: export default async function handler(req, res).

3. Final Answer:

   Missing default export; change to export default async function handler(req, res). -> Option D

4. Quick Check:

   API route default export required = C [OK]

Hint: API routes need default export function [OK]

Common Mistakes:

• Using named export instead of default export
• Confusing API routes with server actions syntax
• Incorrect response method usage

5. You want to build a Next.js app that needs a public API for multiple clients and also some simple server logic tightly integrated with components. Which approach should you choose?

hard

A. Use API routes for the public API and server actions for simple server logic inside components.

B. Use only server actions for everything to keep code simple.

C. Use only API routes for all server logic to avoid confusion.

D. Use client-side fetching only; avoid server code.

Solution

1. Step 1: Analyze app needs

   The app requires a public API accessible by multiple clients and simple server logic integrated with components.

2. Step 2: Match features to approaches

   API routes are best for broad public APIs; server actions are ideal for simple, direct server calls from components.

3. Final Answer:

   Use API routes for the public API and server actions for simple server logic inside components. -> Option A

4. Quick Check:

   Public API + integrated logic = A [OK]

Hint: Public API = API routes; simple logic = server actions [OK]

Common Mistakes:

• Using only server actions for public APIs
• Using only API routes for simple component logic
• Avoiding server code when needed