Book Image

State Management with React Query

By : Daniel Afonso
Book Image

State Management with React Query

By: Daniel Afonso

Overview of this book

State management, a crucial aspect of the React ecosystem, has gained significant attention in recent times. While React offers various libraries and tools to handle state, each with different approaches and perspectives, one thing is clear: state management solutions for handling client state are not optimized for dealing with server state. React Query was created to address this issue of managing your server state, and this guide will equip you with the knowledge and skills needed to effectively use React Query for state management. Starting with a brief history of state management in the React ecosystem, you’ll find out what prompted the split from a global state to client and server state and thus understand the need for React Query. As you progress through the chapters, you'll see how React Query enables you to perform server state tasks such as fetching, caching, updating, and synchronizing your data with the server. But that’s not all; once you’ve mastered React Query, you’ll be able to apply this knowledge to handle server state with server-side rendering frameworks as well. You’ll also work with patterns to test your code by leveraging the testing library and Mock Service Worker. By the end of this book, you'll have gained a new perspective of state and be able to leverage React Query to overcome the obstacles associated with server state.
Table of Contents (14 chapters)
Part 1: Understanding State and Getting to Know React Query
Part 2: Managing Server State with React Query

Why should I use React Query with server-side rendering frameworks?

SSR has proven to be a good ally to web developers. With an increase in the popularity of full-stack frameworks such as Next.js and, most recently, Remix, the React ecosystem has changed, leading to new patterns being applied.

What is server-side rendering (SSR)?

SSR is a process that allows you to render your application on the server instead of the browser. During this process, the server sends the rendered page to the client. The client then makes the page fully interactive through a process called hydration.

Owing to the possibility of using SSR, one of the things that might make sense to do is fetch your data on the server. This has many advantages, but one of the best is giving your users their pages with the initial data already loaded. Now, just because you are loading data on the server side doesn’t invalidate the scenarios in which you might need to fetch your data on the client side. If your...