redux-persist VS react-query

Storage: redux-persist, @react-native-async-storage/async-storage

Next, following their official document, I added some changes to my store.

redux-persist : For persisting data locally

One thing to keep in mind with persisting data to a device is that you maybe have to run migrations on that data if your app starts to use that data differently. https://github.com/rt2zz/redux-persist/blob/master/docs/migrations.md

for most applications, AsyncStorage works fine. also, you can use it with redux-persist or persist middleware of zustand. in this way, you won't even need to touch the AsyncStorage. my first choice as a database (or just a persistor tool) is zustand and AsyncStorage. this combination can solve storage issues most of the time.

That is also admittedly not very smart. Maybe you only want to persist certain slices, maybe you need to do other things with it. That's why https://github.com/rt2zz/redux-persist and other similar addons exist.

react-query

React Query: This library makes it easy to manage data in your React applications, from fetching to caching and updating data. It offers a simple, powerful, and flexible API for handling data and keeping your UI in sync with your data. https://github.com/tannerlinsley/react-query

useQuery (react-query) (+) all from above (+) even more features (-) more complex, even the examples are complex, has more aggressive defaults (re-fetching every 2s)

see here Overview

Rapini is a new tool that can generate custom React Query hooks using OpenAPI (Swagger) files.

React Query is the gold standard for using async data declaratively with hooks. I ended up needing to modify even my simple useTimer hook to work more like useQuery to take multiple keys in order to work as an inner observable for other operators.

For most situations, I would recommend using a library like React Query. It handles a lot of common data-fetching boiler plate and already accounts for this useEffect() issue. Also, it supports Suspense if you want to use that.

At this point, I want to move on to the react-query cache management library. Give a brief overview and see how you can improve your developer experience with cache using this library.

There isn't the "service" concept in React. If you need to send off data you can just do so with fetch. If you need to load data and cache it so it can be used across components and unmounts, then something like react-query is what I'd recommend. But it's basically a combination of React Context, useEffect, and useState to manage the cache and lifecycle of a request.

react-query is pretty neat too. I default to that for most projects unless it's something unusual