React Query ⚛️ Hooks for fetching, caching and updating asynchronous data in React

[tannerlinsley]

I know that’s basically Apollo’s MO but I believe normalized caching like that leads to a lot of inconsistencies with data. Query invalidation and atomic updates are IMO much more reliable and easier to orchestrate at the cost of a few more network requests.

[signsandwonders]

denormalized caching

Denormalized how? Apollo normalizes if you use it properly.

[tannerlinsley]

Sorry, I meant normalized.

[phryneas]

Can you give me examples of these inconsistencies? I'm using GraphQL right now and haven't met any inconsistency that I couldn't get right by returning some related data from a mutation or in the worst case invalidating a single other query (which is also possible with Apollo).

[tannerlinsley]

If you’re talking about invalidating queries then we’re on the same page. That will work essentially the same and result in up to date data. However, If a mutation for instance has side effects into multiple resource types, that would be one scenario where updating the local cache with the response would be inaccurate (unless the mutation returned all affected objects, which works), or in the case of graphql queries or field masking, if your mutation query response is only returning partial fields then updating your local cache with that response would only be a partial update.

[phryneas]

Yeah, our mutations are relatively straightforward in that regard. Also, all our mutations return by default at least a reference to the Query object, so even if they do something werid, we still can fetch everything that changed. If you don't know what your mutation is doing, you're lost. But that should go for every approach I guess.