Why server actions simplify mutations in NextJS - Performance Evidence

Performance: Why server actions simplify mutations

MEDIUM IMPACT

This concept affects interaction responsiveness and reduces client-side bundle size by moving mutation logic to the server.

Updating data on user interaction in a Next.js app

NextJS

'use server';

export async function increment() {
  // Server-side mutation logic
  await db.incrementCounter();
}

export default function Counter() {
  return <form action={increment}>
    <button type="submit">Increment</button>
  </form>;
}

Mutation runs on the server, removing mutation code from client bundle and reducing network overhead, improving input responsiveness.

📈 Performance GainSaves ~5-10kb client bundle; reduces network requests; improves INP by handling mutation server-side

Updating data on user interaction in a Next.js app

NextJS

import { useState } from 'react';

export default function Counter() {
  const [count, setCount] = useState(0);

  async function increment() {
    // Client-side mutation with fetch
    await fetch('/api/increment', { method: 'POST' });
    setCount(count + 1);
  }

  return <button onClick={increment}>Count: {count}</button>;
}

Mutation logic runs on the client and requires extra client-side code and API calls, increasing bundle size and causing slower input response.

📉 Performance CostAdds ~5-10kb to client bundle; triggers multiple network requests; blocks input responsiveness during fetch

Performance Comparison

Pattern	Client Bundle Size	Network Requests	Input Responsiveness	Verdict
Client-side mutation with fetch	Larger (+5-10kb)	Multiple requests	Slower due to fetch wait	[X] Bad
Server actions for mutations	Smaller (saves 5-10kb)	Fewer requests, form submit	Faster input response	[OK] Good

Rendering Pipeline

Server actions move mutation logic from client to server, reducing client-side JavaScript parsing and execution. This reduces the time spent in scripting and network requests on the client, improving interaction responsiveness.

→Scripting

→Network

→Input Handling

⚠️ BottleneckClient-side scripting and network latency during mutation calls

Core Web Vital Affected

INP

This concept affects interaction responsiveness and reduces client-side bundle size by moving mutation logic to the server.

Optimization Tips

1Move mutation logic to server actions to reduce client bundle size.

2Server actions reduce network requests and improve input responsiveness.

3Improved input responsiveness directly benefits the INP Core Web Vital.

Performance Quiz - 3 Questions

How do server actions improve input responsiveness compared to client-side mutations?

A By increasing client bundle size to handle mutations faster

B By moving mutation logic to the server, reducing client scripting and network overhead

C By caching mutation results on the client

D By delaying mutation until after page load

DevTools: Performance

How to check: Record a user interaction that triggers a mutation. Look at scripting time and network requests related to mutation.

What to look for: Long scripting blocks and multiple fetch requests indicate client-side mutation; minimal scripting and fewer requests indicate server actions.

Practice

1. What is the main benefit of using server actions in Next.js for mutations?

easy

A. They make your app slower by adding extra network requests.

B. They require you to write more client-side code for handling state.

C. They allow you to update data directly on the server without extra API calls.

D. They only work with static data and cannot handle dynamic updates.

Solution

1. Step 1: Understand server actions role

   Server actions let you run code on the server side directly from your components.

2. Step 2: Identify how mutations are simplified

   By running mutations on the server, you avoid extra API calls and client-side state management.

3. Final Answer:

   They allow you to update data directly on the server without extra API calls. -> Option C

4. Quick Check:

   Server actions simplify mutations = They allow you to update data directly on the server without extra API calls. [OK]

Hint: Server actions run on server, no extra API calls needed [OK]

Common Mistakes:

• Thinking server actions increase client code
• Believing server actions slow down the app
• Confusing server actions with static data only

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

easy

A. export async function updateData() { /* server code */ }

B. const updateData = () => { /* client code */ }

C. function updateData() { return fetch('/api') }

D. export default function updateData() { /* client code */ }

Solution

1. Step 1: Recognize server action syntax

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

2. Step 2: Check options for server-side export

   Only export async function updateData() { /* server code */ } exports an async function suitable for server actions.

3. Final Answer:

   export async function updateData() { /* server code */ } -> Option A

4. Quick Check:

   Server action syntax = export async function updateData() { /* server code */ } [OK]

Hint: Server actions are exported async functions [OK]

Common Mistakes:

• Using arrow functions without export
• Writing client-side fetch inside server action
• Not marking function as async

3. Given this server action and component code, what will happen when the button is clicked?

export async function incrementCounter() {
  // Imagine this updates a database
  return 1;
}

export default function Counter() {
  const [count, setCount] = React.useState(0);
  async function handleClick() {
    const result = await incrementCounter();
    setCount(count + result);
  }
  return Count: {count};
}

medium

A. The count will increase by 1 each time the button is clicked.

B. The count will stay at 0 because server actions cannot be called from client code.

C. The code will cause a syntax error due to async function usage.

D. The count will increase by 0 because incrementCounter returns nothing.

Solution

1. Step 1: Understand server action return value

   incrementCounter returns 1 simulating a database update.

2. Step 2: Analyze handleClick behavior

   handleClick awaits incrementCounter and adds the result to count state.

3. Final Answer:

   The count will increase by 1 each time the button is clicked. -> Option A

4. Quick Check:

   Server action returns 1, count increments by 1 [OK]

Hint: Server action returns value used to update state [OK]

Common Mistakes:

• Assuming server actions can't be awaited
• Thinking async causes syntax errors
• Ignoring the returned value from server action

4. Identify the error in this server action usage:

export async function saveData() {
  await fetch('/api/save', { method: 'POST' });
}

export default function SaveButton() {
  function handleClick() {
    saveData();
    alert('Saved!');
  }
  return Save;
}

medium

A. saveData must return a value to be valid.

B. handleClick should be async and await saveData to ensure save completes before alert.

C. alert cannot be called inside React components.

D. fetch cannot be used inside server actions.

Solution

1. Step 1: Check async usage in handleClick

   handleClick calls saveData but does not await it, so alert runs immediately.

2. Step 2: Fix by making handleClick async and awaiting saveData

   This ensures data is saved before alert shows.

3. Final Answer:

   handleClick should be async and await saveData to ensure save completes before alert. -> Option B

4. Quick Check:

   Await server action before alert = handleClick should be async and await saveData to ensure save completes before alert. [OK]

Hint: Await async server actions before next steps [OK]

Common Mistakes:

• Not awaiting async functions causing race conditions
• Thinking fetch is disallowed in server actions
• Misunderstanding alert usage in React

5. You want to update a user's profile and then refresh the UI with the new data using server actions. Which approach best uses server actions to simplify this mutation?

1. Create a server action to update the profile.
2. Call the server action directly from the component.
3. Use React state to store updated profile.
4. Avoid extra API calls or client-side fetching.

hard

A. Use server actions only for reading data, not for mutations.

B. Use client-side fetch to call an API route, then update React state with the response.

C. Update profile data only on the client and sync later with server using polling.

D. Define an async server action that updates the profile and returns updated data, then update React state with this data after awaiting the action.

Solution

1. Step 1: Use server action for mutation and return updated data

   This avoids extra API calls and keeps logic on server.

2. Step 2: Await server action in component and update React state

   This refreshes UI with new data immediately and simply.

3. Final Answer:

   Define an async server action that updates the profile and returns updated data, then update React state with this data after awaiting the action. -> Option D

4. Quick Check:

   Server action mutation + update state = Define an async server action that updates the profile and returns updated data, then update React state with this data after awaiting the action. [OK]

Hint: Return updated data from server action and update state [OK]

Common Mistakes:

• Using client fetch instead of server actions
• Not updating React state after mutation
• Thinking server actions can't return data