Skip to main content
The App Router lets you fetch data directly inside components using async/await. Server Components run on the server, so you can safely query databases and external APIs without exposing credentials to the client.

​
Server Components

​
With the fetch API

Turn a component into an async function and await the fetch call: 
export default async function Page() {
  const data = await fetch('https://api.vercel.app/blog')
  const posts = await data.json()

  return (
    <ul>
      {posts.map((post) => (
        <li key={post.id}>{post.title}</li>
      ))}
    </ul>
  )
}
Identical fetch requests in a React component tree are memoized by default, so you can fetch data in the component that needs it instead of drilling props. fetch results are not cached unless you use the use cache directive.

​
With an ORM or database

Since Server Components run on the server, credentials and query logic are never included in the client bundle: 
import { db, posts } from '@/lib/db'

export default async function Page() {
  const allPosts = await db.select().from(posts)

  return (
    <ul>
      {allPosts.map((post) => (
        <li key={post.id}>{post.title}</li>
      ))}
    </ul>
  )
}

​
Client Components

​
With the use API

Start a fetch in your Server Component and pass the unawaited promise to a Client Component: 
import Posts from '@/app/ui/posts'
import { Suspense } from 'react'

export default function Page() {
  // Don't await — pass the promise directly
  const posts = getPosts()

  return (
    <Suspense fallback={<div>Loading...</div>}>
      <Posts posts={posts} />
    </Suspense>
  )
}

'use client'
import { use } from 'react'

export default function Posts({
  posts,
}: {
  posts: Promise<{ id: string; title: string }[]>
}) {
  const allPosts = use(posts)

  return (
    <ul>
      {allPosts.map((post) => (
        <li key={post.id}>{post.title}</li>
      ))}
    </ul>
  )
}

​
With community libraries

Use SWR or React Query for client-side data fetching with caching and revalidation semantics: 
'use client'
import useSWR from 'swr'

const fetcher = (url: string) => fetch(url).then((r) => r.json())

export default function BlogPage() {
  const { data, error, isLoading } = useSWR(
    'https://api.vercel.app/blog',
    fetcher
  )

  if (isLoading) return <div>Loading...</div>
  if (error) return <div>Error: {error.message}</div>

  return (
    <ul>
      {data.map((post: { id: string; title: string }) => (
        <li key={post.id}>{post.title}</li>
      ))}
    </ul>
  )
}

​
Parallel data fetching

Multiple sequential await calls inside a component will run one after another. To fetch data in parallel, initiate requests before awaiting them: 
export default async function Page({ params }) {
  const { username } = await params
  // getAlbums is blocked until getArtist resolves
  const artist = await getArtist(username)
  const albums = await getAlbums(username)
  return <div>{artist.name}</div>
}
If one request fails with Promise.all, the entire operation fails. Use Promise.allSettled to handle partial failures gracefully.

​
Sequential data fetching with Suspense

When one request depends on the result of another, use Suspense to stream the dependent component while showing a fallback: 
export default async function Page({
  params,
}: {
  params: Promise<{ username: string }>
}) {
  const { username } = await params
  const artist = await getArtist(username)

  return (
    <>
      <h1>{artist.name}</h1>
      {/* Streams in once artistID is available */}
      <Suspense fallback={<div>Loading playlists...</div>}>
        <Playlists artistID={artist.id} />
      </Suspense>
    </>
  )
}

async function Playlists({ artistID }: { artistID: string }) {
  const playlists = await getArtistPlaylists(artistID)

  return (
    <ul>
      {playlists.map((playlist) => (
        <li key={playlist.id}>{playlist.name}</li>
      ))}
    </ul>
  )
}

​
Sharing data with React.cache

Use React.cache to deduplicate identical requests across a component tree, and share the result between Server Components and context-based Client Components: 
import { cache } from 'react'

export const getUser = cache(async () => {
  const res = await fetch('https://api.example.com/user')
  return res.json()
})
Create a context provider that stores the promise: 
'use client'

import { createContext } from 'react'

type User = { id: string; name: string }

export const UserContext = createContext<Promise<User> | null>(null)

export default function UserProvider({
  children,
  userPromise,
}: {
  children: React.ReactNode
  userPromise: Promise<User>
}) {
  return <UserContext value={userPromise}>{children}</UserContext>
}
In a layout, pass the unawaited promise to the provider: 
import UserProvider from './user-provider'
import { getUser } from './lib/user'

export default function RootLayout({
  children,
}: {
  children: React.ReactNode
}) {
  const userPromise = getUser() // Don't await

  return (
    <html>
      <body>
        <UserProvider userPromise={userPromise}>{children}</UserProvider>
      </body>
    </html>
  )
}
Client Components resolve the promise from context using use(): 
'use client'

import { use, useContext } from 'react'
import { UserContext } from '../user-provider'

export function Profile() {
  const userPromise = useContext(UserContext)
  if (!userPromise) throw new Error('Must be used within UserProvider')
  const user = use(userPromise)
  return <p>Welcome, {user.name}</p>
}
Server Components can call getUser() directly — React.cache ensures the result is memoized and not fetched twice: 
import { getUser } from '../lib/user'

export default async function DashboardPage() {
  const user = await getUser() // Cached - no duplicate fetch
  return <h1>Dashboard for {user.name}</h1>
}
React.cache is scoped to the current request only. Each request gets its own memoization scope with no sharing between requests.

Build docs developers (and LLMs) love

Get started for freeTalk to us