#Loader SWR on part of the data

1 messages · Page 1 of 1 (latest)

dim coral
#

I'm building a site like bbc.com. I want to use stale-while-revalidate for the top headlines, so everyone gets the same data and gets it as quickly as possible.

Further down the page is more personalised content. That stuff shouldn't be cached at all (except maybe in the browser), because it's dependant on the user.

As far as I understand, to use SWR with headers, it's all route-based, and that won't work because I want different caching within the '/' route. My thought is I could have an in-memory cache on each app server which does SWR, and there I would put the top headlines.

Does this sound feasible? It seems like a common problem, but the main SWR lib I see is the frontend one. Does anyone have experience with a good library for doing the same thing on the backend without building it from scratch? Is this approach sounding crazy? I'd rather not introduce the complexity of a separate caching system like redis if I can get away with it, and the size of the cached data is going to be tiny

fair ocean
#

I recently implemented a small and simple in-memory cache for a particularly slow endpoint that may point you to the right direction:

https://github.com/manawiki/core/commit/d5a0fae8ad89276d2fdd6487c6f5b203937de347#diff-744f0c9c3f34b015401a3ad2d11154de3acd7bc3127419387fc626a23692fb20

GitHub
Implement _layout `lru-cache` to improve response time · manawiki/c...

_layout.tsx response slows the whole site. Since the api query by it doesn't change often, we'll implement a 5 min server cache for this using lru-cache

https://sergiodxa.com/artic...

#

There are more established strategies, like using cachified but this is the least effort option I'm aware of that wouldn't lead to memory leaks, and give you just enough to a/b test performance.