Lesson 3.1
Fetching data in server components
A server component can simply await its data. No client-side loading state, no waterfall of effects, and no exposed credentials.
4mIntermediate12,586 students
Sign in to watch this lesson
Browsing is free. Create an account to play videos and track your progress.
Overview
A server component can simply await its data. No client-side loading state, no waterfall of effects, and no exposed credentials.
What this lesson covers
- Await data directly inside an async server component
- Fetch in parallel instead of sequential waterfalls
- Keep tokens and database access on the server
This lesson sits in Data Fetching and Caching, part of Next.js App Router in Depth. It assumes what came before it and leads directly into the next lesson in the module.
In this lesson you will:
- Await data directly inside an async server component
- Fetch in parallel instead of sequential waterfalls
- Keep tokens and database access on the server