Client side cache best practices
Hi!
Finally getting my hands on TanStack and I love it so far. One question I have though is regarding cache best practices when it comes to invalidate vs manually update it.
Say I have a simple CRUD api:
The main thing from this API is that some queries say
When using
For the
And to some extent one could argue that once I have the initial state of my app, then I could always rely on manually updating the cache and never actually refetc the data from the server. So my main question is to which extent is it considered good or bad practice? When invalidating cache is better over manually updating it?
Another related question: is updating the cache "thread safe" (or async context is maybe more precise)? Not sure if it really means something in JS but basically if the same mutation is called twice and the
Finally getting my hands on TanStack and I love it so far. One question I have though is regarding cache best practices when it comes to invalidate vs manually update it.
Say I have a simple CRUD api:
The main thing from this API is that some queries say
DELETE /api/services/[service-id]GET /api/hospitals/[hospital-id]/servicesGET /api/hospitals/[hospital-id]When using
useMutationDELETE_SERVICEHOSPITAL_SERVICESHOSPITALFor the
HOSPITAL_SERVICES{serviceId, serviceName}HOSPITALserviceCountAnd to some extent one could argue that once I have the initial state of my app, then I could always rely on manually updating the cache and never actually refetc the data from the server. So my main question is to which extent is it considered good or bad practice? When invalidating cache is better over manually updating it?
Another related question: is updating the cache "thread safe" (or async context is maybe more precise)? Not sure if it really means something in JS but basically if the same mutation is called twice and the
onSuccessserviceCount
