7 of 3023%

beginnerNext.js23% complete

Server Components

Learn Server Components through app route: what it does, when to use it, the code pattern, and a small task you can test immediately.

Run example Practice

This lesson gives you

3 Working code

3 Practice tasks

5 Interview answers

Plain meaning

Server Components is a Next.js pattern for one practical job. Learn the input, apply the smallest working syntax, check the output, then reuse the pattern in a real feature.

Why it matters

Server Components matters because real Next.js work needs consistent ways to render React server components. Without this pattern, the feature becomes harder to change, test and review.

Real use

In a real project, server components helps build an SEO-optimized blog layout using dynamic params, static paths and search queries.

Working example

Core pattern

This is the version to read first, run next, and modify last.

// NextJS Server Component
import { SITE_URL } from "@/lib/constants";

export default async function Page() {
  const res = await fetch(`${SITE_URL}/api/orders`);
  const orders = await res.json();
  return <main><h1>Orders ({orders.length})</h1></main>;
}

Expected output

NextJS pre-renders page static HTML during build or dynamic JSON on runtime fetch.

Line by line

What each part does

Line 1 sets up the Server Components example: // NextJS Server Component.

Line 2 adds one required part of the working pattern: import { SITE_URL } from "@/lib/constants";.

Line 3 adds one required part of the working pattern: blank line.

Line 4 adds one required part of the working pattern: export default async function Page() {.

Line 5 adds one required part of the working pattern: const res = await fetch(`${SITE_URL}/api/orders`);.

Line 6 adds one required part of the working pattern: const orders = await res.json();.

Methods and commands

Server Components reference

Use these methods, commands, tags or properties with the working example above.

ServerComponent

async function Page()

Fetch data and render layouts on server side.

export default async function Page() { return <h1>Layout</h1>; }

ServerAction

'use server'; async function save()

Invoke secure server tasks directly from client triggers.

async function save(data) { 'use server'; await db.save(data); }

Metadata

export const metadata: Metadata

Configure page SEO titles and meta tags statically or dynamically.

export const metadata = { title: 'SEO Ready' };

Try it yourself

Edit and run the concept

Change one thing at a time so the output stays easy to understand.

Next.js Server Components editor

lesson.jsjavascript

javascript8 linesWrap

Input

Wrap

Terminal

Success

Ready.

Run code to see output here.

Examples

Three useful variations

Compare the examples by level. Each one keeps the same idea but changes the situation.

Beginner example

javascript

// NextJS Server Component
import { SITE_URL } from "@/lib/constants";

export default async function Page() {
  const res = await fetch(`${SITE_URL}/api/orders`);
  const orders = await res.json();
  return <main><h1>Orders ({orders.length})</h1></main>;
}

NextJS pre-renders page static HTML during build or dynamic JSON on runtime fetch.

Intermediate example

javascript

// NextJS Server Component
import { SITE_URL } from "@/lib/constants";

export default async function Page() {
  const res = await fetch(`${SITE_URL}/api/orders`);
  const orders = await res.json();
  return <main><h1>Orders ({orders.length})</h1></main>;
}

NextJS pre-renders page static HTML during build or dynamic JSON on runtime fetch.

Advanced example

javascript

// NextJS Server Component
import { SITE_URL } from "@/lib/constants";

export default async function Page() {
  const res = await fetch(`${SITE_URL}/api/orders`);
  const orders = await res.json();
  return <main><h1>Orders ({orders.length})</h1></main>;
}

NextJS pre-renders page static HTML during build or dynamic JSON on runtime fetch.

Practice

Build understanding

Rewrite the Server Components example for app route using your own labels or data.

Add one edge case from dynamic params, static paths and search queries and record the output.

Explain where Server Components fits inside an SEO-optimized blog layout.

Mini task

Build a tiny an SEO-optimized blog layout step that uses Server Components, then write the expected output before running it.

Checklist

Use it correctly

Server Components is easier when connected to a real task.
Small examples are the fastest way to catch misunderstandings.
Practice, quiz review and projects reinforce the lesson.
Line-by-line review turns copied code into understood code.

Common mistake

Skipping the small server components example and trying to memorize the rule first.

Best practice

Use descriptive names so the example explains itself.

Interview prep

Server Components questions

Use these as concise model answers, then rewrite them in your own words.

1. What is Server Components in Next.js?

Server Components is a specific Next.js pattern used to make a common task easier to read, write, test, or explain. A strong answer includes the purpose, a tiny example, and the result you expect after running it.

2. Why do developers use server components?

Server Components matters because real Next.js work needs consistent ways to render React server components. Without this pattern, the feature becomes harder to change, test and review.

3. How would you use server components in a real project?

In a real project, server components helps build an SEO-optimized blog layout using dynamic params, static paths and search queries. Start with the simple syntax, keep names clear, run the code, then handle one edge case before expanding the feature.

4. What mistake should a beginner avoid with server components?

Skipping the small server components example and trying to memorize the rule first.

5. How would you explain NextJS Introduction in Next.js during an interview?

NextJS Introduction is best explained with its purpose, a small example, and one common mistake.

6. How would you explain App Router Basics in Next.js during an interview?

App Router Basics is best explained with its purpose, a small example, and one common mistake.

Simple rule

Start with the working example, change one value, run it again, and explain why the output changed. That makes server components useful instead of memorized.