Effect's Caching and Invalidation Capabilities Compared to TanStack Query
Hi everyone,
I’ve seen some Reddit posts suggesting that Effect can replicate the functionality of TanStack Query. I’m having trouble understanding Effect does it have like handles caching and cache invalidation.
Does Effect provide a built-in mechanism for caching and invalidating data, similar to TanStack Query? If not, how would I go about creating a helper function or utility to handle caching and invalidation myself?
For context, I’m using Svelte + Hono in my project. and i wanted a easy way to "Cache" Fetched data and be able to mutate or invalidate it similar to Tanstack Query
I’ve seen some Reddit posts suggesting that Effect can replicate the functionality of TanStack Query. I’m having trouble understanding Effect does it have like handles caching and cache invalidation.
Does Effect provide a built-in mechanism for caching and invalidating data, similar to TanStack Query? If not, how would I go about creating a helper function or utility to handle caching and invalidation myself?
For context, I’m using Svelte + Hono in my project. and i wanted a easy way to "Cache" Fetched data and be able to mutate or invalidate it similar to Tanstack Query
