Turn a data-fetching waterfall into parallel requests

Three awaits, three round trips, one after another, for data that never depended on each other.

Intermediate to advancedRead 5 minDoing: under an hour6 steps

What you'll have at the end

The three independent reads running together under Promise.all, and the page's own duration collapsed from the sum of the three to just the slowest one

Before you start

You need

A Server Component whose body awaits three or more independent reads one after another, each needing only an id already in scope, where one read (an internal billing call) is both the slowest and the least reliable of the three.

Not covered

Streaming the three panels independently with Suspense so a fast one paints before the slowest resolves, and speeding up the slow billing call itself; both are real further wins, but this recipe only removes the wait that came from running the three in a line.

Leans on

6 steps

Where to go next

Replace a manual fetch effect with TanStack Query

when the three reads live in a Client Component instead of a Server Component, TanStack Query's useQueries runs them concurrently the same way, without touching this recipe's Server Component code.

Checked 25 Aug 2026

Part of the NextJS cookbook