Book Image

Micro State Management with React Hooks

By : Daishi Kato
Book Image

Micro State Management with React Hooks

By: Daishi Kato

Overview of this book

State management is one of the most complex concepts in React. Traditionally, developers have used monolithic state management solutions. Thanks to React Hooks, micro state management is something tuned for moving your application from a monolith to a microservice. This book provides a hands-on approach to the implementation of micro state management that will have you up and running and productive in no time. You’ll learn basic patterns for state management in React and understand how to overcome the challenges encountered when you need to make the state global. Later chapters will show you how slicing a state into pieces is the way to overcome limitations. Using hooks, you'll see how you can easily reuse logic and have several solutions for specific domains, such as form state and server cache state. Finally, you'll explore how to use libraries such as Zustand, Jotai, and Valtio to organize state and manage development efficiently. By the end of this React book, you'll have learned how to choose the right global state management solution for your app requirement.
Table of Contents (16 chapters)
1
Part 1: React Hooks and Micro State Management
3
Part 2: Basic Approaches to the Global State
8
Part 3: Library Implementations and Their Uses

Using the data-centric and component-centric approaches

Global state can technically be divided into two types: data-centric and component-centric.

In the following sections, we will discuss both these approaches in detail. Then, we will also talk about some exceptions.

Understanding the data-centric approach

When you design an app, you may have a data model as a singleton in your app and you may already have the data to deal with. In this case, you would define components and connect the data and the components. The data can be changed from the outside, such as by other libraries or from other servers.

For the data-centric approach, module state would fit better, because module state resides in JavaScript memory outside React. Module state can exist before React starts rendering or even after all React components are unmounted.

Global state libraries using the data-centric approach would provide APIs to create module state and to connect the module state to React components...