Pengambilan Data Sisi Server
Implementasikan pengambilan data sisi server yang tangguh menggunakan `fetch` dan metode lain dalam Server Components untuk kinerja optimal.
Pengambilan Data Sisi Server adalah pelajaran Next.js 15 Fullstack (App Router + Server Actions) gratis di CoddyKit. Ini adalah pelajaran 1 dari 3. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Next.js 15 Fullstack (App Router + Server Actions), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Next.js 15 Fullstack (App Router + Server Actions) mencakup 3 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Why Fetch Data on the Server?
Next.js 15 excels at rendering your application on the server. This is super powerful for performance and SEO!
When you fetch data directly on the server, your users see content faster because the HTML is already built with data. It also helps search engines index your content better.
- Performance: Faster initial page loads.
- SEO: Content is available for crawlers.
- Security: Keep sensitive logic on the server.
Enhanced `fetch` for Server Components
In Next.js 15 Server Components, the standard fetch Web API is automatically enhanced. This means it comes with built-in caching and revalidation features.
You can use fetch directly inside your async Server Components to get data from external APIs or your own backend services.
Fetching Data in a Component
Let's see how simple it is to fetch data. Here, we'll get a single "Todo" item from a public API. Notice the async keyword on the component function.
Next.js handles the waiting for data before rendering the component.
Run This Basic Fetch Example
This JavaScript code demonstrates fetching data from a public API. While a Next.js Server Component uses JSX, the underlying fetch logic is the same. Run it to see the data!
async function fetchTodo() {
const url = 'https://jsonplaceholder.typicode.com/todos/1';
try {
const response = await fetch(url);
if (!response.ok) {
throw new Error(`HTTP error! status: ${response.status}`);
}
const data = await response.json();
console.log("Fetched Todo Title:", data.title);
} catch (error) {
console.error("Fetch failed:", error);
}
}
fetchTodo();Automatic Caching with `fetch`
By default, Next.js automatically caches the results of fetch requests in Server Components. If the same fetch request is made again (e.g., across multiple components or re-renders), Next.js will use the cached data.
This is fantastic for performance as it avoids redundant network requests.
Opting Out of Caching
Sometimes, you need the freshest data, bypassing the cache. You can do this by passing an option to fetch: { cache: 'no-store' }. This tells Next.js to always refetch the data.
Use 'no-store' for highly dynamic data that changes frequently and needs to be up-to-date on every request.
async function fetchFreshData() {
const url = 'https://jsonplaceholder.typicode.com/posts/1';
// 'no-store' ensures data is always fresh
const response = await fetch(url, { cache: 'no-store' });
const data = await response.json();
console.log("Fresh Post Title:", data.title);
}
fetchFreshData();Revalidating Data on Demand
What if you want cached data, but also want to specify how often it should be considered "fresh"? You can use the next.revalidate option with fetch.
This sets a time-to-live (TTL) for the data. After this time, the next request will refetch the data and update the cache.
async function fetchRevalidatedData() {
const url = 'https://jsonplaceholder.typicode.com/users/1';
// Revalidate data every 60 seconds
const response = await fetch(url, { next: { revalidate: 60 } });
const data = await response.json();
console.log("User Name (revalidated):", data.name);
}
fetchRevalidatedData();`revalidate` vs. `no-store`
Choosing between cache: 'no-store' and next: { revalidate: N } depends on your data's needs:
no-store: Use for data that must be absolutely fresh on every request (e.g., real-time stock prices, user-specific shopping cart).revalidate: N: Use for data that can be slightly stale but should update periodically (e.g., blog posts, product listings that change hourly).- Default (cached): Use for static or infrequently changing data (e.g., navigation links, static page content).
Beyond `fetch`: Direct Database Access
While fetch is powerful for external APIs, Server Components can also directly interact with databases or ORMs like Prisma. Since Server Components run on the server, they can safely contain database credentials.
This means you can write code like await prisma.user.findMany() directly in your components, keeping your client bundle small and secure.
Data Fetching Options
Which of the following statements about server-side data fetching in Next.js 15 are TRUE?
Recap: Server-Side Fetching
You've learned how to harness server-side data fetching in Next.js 15!
fetchin Server Components is automatically optimized with caching.- Use
cache: 'no-store'for always-fresh data. - Use
next: { revalidate: N }for time-based data freshness. - Server Components can also directly access databases securely.
Mastering these techniques is key to building fast, efficient, and secure Next.js applications.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pengambilan Data Sisi Server” gratis?
Ya — teks lengkap “Pengambilan Data Sisi Server” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Next.js 15 Fullstack (App Router + Server Actions), upgrade ke CoddyKit PRO. Kursus Next.js 15 Fullstack (App Router + Server Actions) mencakup 3 pelajaran total.
Apa yang akan aku pelajari di “Pengambilan Data Sisi Server”?
Implementasikan pengambilan data sisi server yang tangguh menggunakan `fetch` dan metode lain dalam Server Components untuk kinerja optimal. Kamu berlatih Next.js 15 Fullstack (App Router + Server Actions) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Next.js 15 Fullstack (App Router + Server Actions)?
Tidak diperlukan pengalaman sebelumnya. Next.js 15 Fullstack (App Router + Server Actions) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 3.
Berapa lama pelajaran “Pengambilan Data Sisi Server” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Next.js 15 Fullstack (App Router + Server Actions) ini?
Ya. Setiap pelajaran Next.js 15 Fullstack (App Router + Server Actions) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Pengambilan Data Sisi Server
- Penyimpanan Sementara & Validasi Ulang
- Pengambilan Data Paralel, Berurutan, dan Streaming