Server State vs Client State Separation
What you'll learn: Why treating server data and UI state as separate concerns prevents architectural chaos.
The Core Problem
When you mix server cache (data from APIs) with client UI state (modals, form inputs, toggles) in the same state management solution, you create a tangled mess. Here's why:
Server state has unique characteristics:
- It's asynchronous and arrives at unpredictable times
- It can become stale and needs revalidation
- Multiple components might need the same data (caching becomes critical)
- It can fail, requiring retry logic
- It lives on the server, you just have a snapshot
Client state is fundamentally different:
- It's synchronous and immediate
- It never becomes stale (it IS the source of truth)
- It's typically local to one component or feature
- It doesn't need refetching or background updates
The Mixing Trap
// Anti-pattern: Everything in one reducer
const [state, dispatch] = useReducer(reducer, {
user: null, // Server state!
posts: [], // Server state!
isModalOpen: false, // Client state
selectedTab: 'home' // Client state
});
This approach forces you to:
- Write loading/error logic for every piece of server data
- Manually invalidate and refetch
- Handle cache deduplication yourself
- Mix sync and async concerns
When Dedicated Libraries Help
Libraries like React Query or SWR specialize in server state: they cache, deduplicate, revalidate, and manage loading states automatically. Your global state manager (Context, Redux, Zustand) then focuses purely on client UI concerns.
Key Takeaway: Separating server state (remote data cache) from client state (UI interactions) creates clear boundaries, reduces complexity, and leverages specialized tools for each domain—dedicated libraries handle the hard parts of remote data so your state logic stays simple.