Server component database queries in NextJS - Step-by-Step Execution

Concept Flow - Server component database queries

Start Server Component Render

↓

Run async DB Query

↓

Wait for DB Response

↓

Receive Data

↓

Render JSX with Data

↓

Send HTML to Client

↓

End

This flow shows how a Next.js server component fetches data from a database asynchronously, waits for the data, then renders the UI with that data before sending HTML to the client.

Execution Sample

NextJS

import { db } from '@/lib/db';

export default async function Users() {
  const users = await db.user.findMany();
  return <ul>{users.map(u => <li key={u.id}>{u.name}</li>)}</ul>;
}

This server component fetches a list of users from the database and renders them as a list.

Execution Table

Step	Action	Evaluation	Result
1	Start rendering Users component	No data yet	Component starts async function
2	Call db.user.findMany()	Await database query	Promise pending
3	Wait for DB response	DB returns user array	[{id:1, name:'Ana'}, {id:2, name:'Ben'}]
4	Map users to JSX list items	Create <li> elements	<li key=1>Ana</li>, <li key=2>Ben</li>
5	Return <ul> with list items	JSX ready	<ul><li>Ana</li><li>Ben</li></ul>
6	Send rendered HTML to client	HTML sent	Client receives user list
7	End rendering	Component done	Render complete

💡 Rendering ends after data is fetched and JSX is returned

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
users	undefined	[{id:1, name:'Ana'}, {id:2, name:'Ben'}]	Same array	Same array

Key Moments - 3 Insights

Why do we use 'await' before the database query?

Because the database query returns a promise, 'await' pauses execution until the data arrives, as shown in execution_table step 2 and 3.

Can we use client-side hooks like useState in server components?

No, server components run on the server and do not support client hooks. The data fetching and rendering happen before sending HTML, as seen in the flow.

What happens if the database query is slow?

The server component waits at step 3 until the data returns, delaying rendering but ensuring fresh data before sending HTML.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'users' after step 3?

A undefined

B Promise pending

C [{id:1, name:'Ana'}, {id:2, name:'Ben'}]

D Empty array

💡 Hint

Check the 'users' variable in variable_tracker after step 3

At which step does the component send HTML to the client?

A Step 6

B Step 5

C Step 4

D Step 7

💡 Hint

Look for 'Send rendered HTML to client' in execution_table

If we remove 'await' before the DB query, what changes in the execution?

A The component renders the list instantly

B The component immediately returns a promise, not data

C The DB query runs synchronously

D No change in behavior

💡 Hint

Consider what happens when you don't wait for a promise in async code

Concept Snapshot

Server components in Next.js can fetch data directly using async/await.
They wait for database queries to complete before rendering.
The rendered HTML with data is sent to the client.
No client-side hooks or state are used here.
This ensures fast, SEO-friendly pages with fresh data.

Full Transcript

In Next.js, server components can fetch data from a database using async functions. The component starts rendering, calls the database query with await, and pauses until the data returns. Once the data arrives, it maps the data to JSX elements and returns the full HTML. This HTML is sent to the client. The process ensures the client gets a fully rendered page with data already included. Server components do not use client hooks like useState. If the database is slow, rendering waits but the client still gets fresh data. Removing await causes the component to return a promise instead of data, breaking rendering.

Practice

1. What is the main advantage of using server components in Next.js for database queries?

easy

A. They fetch data securely on the server without exposing credentials to the client.

B. They allow direct database access from the browser.

C. They require no async/await syntax for queries.

D. They automatically cache data on the client side.

Solution

1. Step 1: Understand server components role

   Server components run on the server, so they can safely access databases without exposing secrets to the client.

2. Step 2: Compare options

   Only They fetch data securely on the server without exposing credentials to the client. correctly states the security advantage. Options A, C, and D are incorrect because database access is not done in the browser, async/await is needed, and caching is not automatic on client side.

3. Final Answer:

   They fetch data securely on the server without exposing credentials to the client. -> Option A

4. Quick Check:

   Server components = secure server data fetching [OK]

Hint: Server components run on server, so data stays secure there [OK]

Common Mistakes:

• Thinking database queries run in the browser
• Ignoring async/await for fetching data
• Assuming client-side caching is automatic

2. Which of the following is the correct way to fetch data from a database inside a Next.js server component?

easy

A. const data = await db.query('SELECT * FROM users')

B. const data = fetch('api/data')

C. const data = db.query('SELECT * FROM users')

D. const data = useEffect(() => db.query('SELECT * FROM users'), [])

Solution

1. Step 1: Identify async database query syntax

   Database queries inside server components must use async/await to wait for the query result.

2. Step 2: Evaluate options

   const data = await db.query('SELECT * FROM users') uses await correctly. const data = fetch('api/data') uses fetch which is client-side. const data = db.query('SELECT * FROM users') misses await, so it returns a promise. const data = useEffect(() => db.query('SELECT * FROM users'), []) uses useEffect, which is a client hook and invalid in server components.

3. Final Answer:

   const data = await db.query('SELECT * FROM users') -> Option A

4. Quick Check:

   Async query = await db.query(...) [OK]

Hint: Use await with db queries inside async server components [OK]

Common Mistakes:

• Omitting await causing unresolved promises
• Using client hooks like useEffect in server components
• Using fetch instead of direct DB queries

3. Given this Next.js server component code, what will be rendered if the database returns [{ id: 1, name: 'Alice' }, { id: 2, name: 'Bob' }]?

export default async function Users() {
  const users = await db.query('SELECT id, name FROM users');
  return (
    <ul>
      {users.map(user => <li key={user.id}>{user.name}</li>)}
    </ul>
  );
}

medium

A. 12

B. AliceBob

C. Error: users.map is not a function

D. {user.name}{user.name}

Solution

1. Step 1: Understand data and rendering

   The database returns an array of user objects with id and name. The component maps over users and renders each name inside <li>.

2. Step 2: Check output correctness

   • Alice
   • Bob
   correctly shows the list with names Alice and Bob.
   • 1
   • 2
   shows ids instead of names. Error: users.map is not a function would happen if users was not an array.
   • {user.name}
   • {user.name}
   shows JSX code as text, which is incorrect.

3. Final Answer:

   <ul><li>Alice</li><li>Bob</li></ul> -> Option B

4. Quick Check:

   Mapping array to list items = names shown [OK]

Hint: Map array to JSX list to render names correctly [OK]

Common Mistakes:

• Rendering ids instead of names
• Forgetting to use key prop in list items
• Trying to render raw objects instead of properties

4. Identify the error in this Next.js server component fetching data from a database:

export default function Products() {
  const products = await db.query('SELECT * FROM products');
  return (
    <div>{products.length} products found</div>
  );
}

medium

A. products.length is invalid for query result

B. Cannot use await inside server components

C. Missing async keyword on the component function

D. db.query should be inside useEffect hook

Solution

1. Step 1: Check async usage in server component

   Await can only be used inside async functions. The component lacks the async keyword.

2. Step 2: Validate other options

   Cannot use await inside server components is wrong because await is allowed in server components if async is used. db.query should be inside useEffect hook is wrong because useEffect is client-only. products.length is invalid for query result is wrong because products is expected to be an array with length.

3. Final Answer:

   Missing async keyword on the component function -> Option C

4. Quick Check:

   Await requires async function [OK]

Hint: Add async before function to use await inside [OK]

Common Mistakes:

• Forgetting async keyword on server component
• Using client hooks like useEffect in server components
• Assuming query result is not an array

5. You want to fetch user data and their posts in a Next.js server component. Which approach correctly fetches both from the database before rendering?

export default async function UserPosts() {
  const user = await db.query('SELECT * FROM users WHERE id = 1');
  const posts = await db.query('SELECT * FROM posts WHERE userId = 1');
  return (
    <section>
      <h1>{user.name}</h1>
      <ul>
        {posts.map(post => <li key={post.id}>{post.title}</li>)}
      </ul>
    </section>
  );
}

What is the best way to optimize these queries?

hard

A. Fetch posts on the client side using useEffect

B. Run the second query inside the map function for posts

C. Combine both queries into one SQL join query

D. Run both queries in parallel using Promise.all before rendering

Solution

1. Step 1: Understand query optimization

   Running queries sequentially waits for the first before starting the second, slowing response.

2. Step 2: Evaluate options for optimization

   Run both queries in parallel using Promise.all before rendering runs both queries in parallel with Promise.all, improving speed. Run the second query inside the map function for posts runs queries inside map, causing many queries (bad). Fetch posts on the client side using useEffect moves fetching to client, losing server benefits. Combine both queries into one SQL join query is possible but may complicate data handling.

3. Final Answer:

   Run both queries in parallel using Promise.all before rendering -> Option D

4. Quick Check:

   Parallel queries = faster data fetching [OK]

Hint: Use Promise.all to fetch multiple queries simultaneously [OK]

Common Mistakes:

• Running queries one after another sequentially
• Fetching data inside loops causing many queries
• Moving server data fetching to client side unnecessarily