การจัดการสถานะเซิร์ฟเวอร์

When building applications, you deal with different kinds of data. Server state refers to data that lives on a remote server, like a list of products, user profiles, or blog posts.

It's distinct from client state, which is data managed purely within your application, such as whether a modal is open or a theme is dark/light.

Managing server state can be tricky because:

• It's Asynchronous: Data isn't instantly available; it takes time to fetch.
• It Can Be Stale: The data on the server might change after you've fetched it.
• Caching is Hard: How do you store fetched data efficiently and know when to refetch?
• Error Handling: Network requests can fail, requiring robust error management.
• Loading States: Users need feedback while data is being fetched.

Libraries like SWR (Stale-While-Revalidate) and React Query (now TanStack Query) are designed specifically to tackle these server state challenges in React applications.

They provide powerful hooks that simplify data fetching, caching, revalidation, and error handling, making your UI more robust and responsive.

Before using a library like SWR, fetching data asynchronously often involves manual handling of loading, success, and error states. Here's a basic JavaScript example:

SWR wraps this fetching logic into a convenient React Hook called useSWR. It automatically provides the data, error, and a loading state (implicitly via data being undefined initially).

You provide a unique key (often the API endpoint) and a fetcher function that makes the actual data request.

One of SWR's core features is its intelligent caching. When multiple components request data with the same key, SWR automatically deduplicates these requests, fetching the data only once.

It then shares this cached data across all subscribers, preventing unnecessary network calls and improving performance. This is crucial for large applications.

SWR's name comes from its Stale-While-Revalidate caching strategy. This means:

• It immediately returns the cached (stale) data to the UI.
• It then sends a request to revalidate (fetch new) data in the background.
• Once new data arrives, it updates the UI.

This provides an instant user experience while ensuring data freshness.

SWR and React Query automatically revalidate data in several common scenarios, ensuring your UI always reflects the latest server state:

• On Focus: When the browser tab or window regains focus.
• On Reconnect: When the network connection is restored.
• On Interval: You can configure periodic revalidation for frequently changing data.

This significantly reduces the need for manual data refreshing.

When you perform actions that change server data (e.g., submitting a form to create a new post), you need to update your UI. SWR provides a mutate function to help with this.

You can use mutate to manually revalidate the data associated with a key, or even update the local cache directly for immediate optimistic UI updates.

You've explored the world of server state and learned why it requires special handling compared to client state. Libraries like SWR and React Query are indispensable tools for Next.js developers, simplifying data fetching, caching, revalidation, and error management.

By leveraging these libraries, you can build more performant, reliable, and user-friendly applications with less effort. Keep practicing these concepts to master your data fetching!