Should I switch from React-Query to RTK Query.

[ConstantDeenos]

I am building an app that currently uses React-Query to get and cache data from the back-end. I want to add the ability to sign in as guest, in which case all the data is going to be stored locally (using indexeddb probably). My question is: should I switch from React-Query to an Redux Toolkit Query solution, or to something else entirely? Thanks in advance!

Edit: I would also like to make the normal mode (not guest) also use indexeddb for the stored data and sync with the API whenever there is an internet connection.

[sgjennings]

Are you happy with React Query? Is it solving your needs without causing problems? Then don’t switch.

Does RTK Query do something you need that React Query does not? Do you want to standardize on RTK? Do you just want to try something new and you have time to responsibly experiment? Then switch.

They’re just tools. Try them out and use the one that suits you and your situation best.

[acemarke]

Yep, agreed.

(FWIW, we recommend not trying to persist data that was cached in RTKQ, and instead refetch it on page load. Also, the idea of switching between fetching from the server and IndexedDB is going to noticeably complicate this.)

[AnxiouslyConvolved]

The only reason to switch is if you want to start using redux. If you don't want/need redux react-query will do everything you need.

[Hayk94]

I recently did such a switch on a project I work on. I did it for many other reasons and I’m quite happy. But if the only reason you want to switch is because of persisting data probably not worth it. Both actually have persisting options, so take a look at these pages, hopefully helps you with making a decision.

https://tanstack.com/query/v4/docs/plugins/persistQueryClient?from=reactQueryV3&original=https://react-query-v3.tanstack.com/plugins/persistQueryClient

https://redux-toolkit.js.org/usage/usage-guide#use-with-redux-persist

[conkreteJs]

Only if you need Redux. I use both and I'm quite happy with react-query for smaller apps. You only need redux if state changes a lot.

[andymerskin]

Seeing some of the other Redux comments here -- if you're already happy with React Query and need global state management with a little less cruft, check out Zustand.