unstable_cache is too unstable for prod. what is the recommended way to cache a prisma fetch.

Answered

Plott Hound posted this in #help-forum

Plott HoundOP

2024-01-29T14:52:11.000Z

given the simple example how would approach caching this:

import prisma from '@/db/prisma';

export async function ListTasks() {
    const allTasks = await prisma.task.findMany();

    return (
        <div>
            {allTasks.map((task) => (
                <div key={task.id}>
                    <p>{task.title}</p>
                </div>
            ))}
        </div>
    )
}

bonus question: based on your choice of caching how would you revalidate that cache.

Thanks

Answered by joulev

what is the recommended way to cache a prisma fetch.

unfortunately, there isn't a better way than unstable_cache. but i am using it and i think it's pretty stable recently

View full answer

30 Replies

@Plott Hound given the simple example how would approach caching this: import prisma from '@/db/prisma'; export async function ListTasks() { const allTasks = await prisma.task.findMany(); return ( <div> {allTasks.map((task) => ( <div key={task.id}> <p>{task.title}</p> </div> ))} </div> ) } bonus question: based on your choice of caching how would you revalidate that cache. Thanks

joulev

2024-01-29T14:52:55.000Z

what is the recommended way to cache a prisma fetch.

unfortunately, there isn't a better way than unstable_cache. but i am using it and i think it's pretty stable recently

Answer

joulev

2024-01-29T14:53:08.000Z

with unstable_cache you can also easily assign tags to revalidate at will

Plott HoundOP

2024-01-29T14:54:39.000Z

thank you. i've also using it with unstable_cache for a few months but i occasionally get strange issues. I'm also using revalidate tag. I just thought i'd ask after seeing some of the discussion in #discussions

it's good enough for me for now but thought i'd ask if there were any good alternatives

joulev

2024-01-29T14:56:08.000Z

yeah i would use the alternatives if they exist as well. but the only alternative i can imagine is that you make it a route handler and fetch it from the server component, which is even worse than using unstable_cache

Ray

2024-01-29T14:57:04.000Z

https://github.com/epicweb-dev/cachified

but will require a redis server if you are hosting on serverless

@joulev yeah i would use the alternatives if they exist as well. but the only alternative i can imagine is that you make it a route handler and fetch it from the server component, which is even worse than using `unstable_cache`

Plott HoundOP

2024-01-29T14:58:32.000Z

thanks. yes this is somewhat a callback to the first post i ever made in this discord weighing up the differences of fetching your own route handler vs unstable cache with a direct fetch in an RSC. and i believe you showed me the next faq page that explained it very well. so thanks again for the help, i'll keep my eye out for updates on unstable_cache and stick with what i have for now ðŸ™‚

@Ray https://github.com/epicweb-dev/cachified

Plott HoundOP

2024-01-29T14:59:09.000Z

interesting! thanks for sharing, i'll try it out in a new project. have you had much experience using this? how did you find it?

im hosting on a server so thats not an issue

@Plott Hound interesting! thanks for sharing, i'll try it out in a new project. have you had much experience using this? how did you find it?

Ray

2024-01-29T14:59:51.000Z

I use it with remix. the author is one of the remix core member

@Ray I use it with remix. the author is one of the remix core member

Plott HoundOP

2024-01-29T15:00:37.000Z

cool. i'll give it a go and see how i get on. its tricky to compare since the issues i get with unstable are few and far between which makes them hard to log and isolate. looks cool though

@Ray https://github.com/epicweb-dev/cachified

joulev

2024-01-29T15:01:19.000Z

cool, so this is a bring-your-own cache solution. will check this out, thanks for telling us about this project

Ray

2024-01-29T15:02:36.000Z

yes and I found unstable_cache doesn't work well on other serverless hostingðŸ˜†

actually the data cache

@Ray yes and I found `unstable_cache` doesn't work well on other serverless hostingðŸ˜†

Plott HoundOP

2024-01-29T15:03:22.000Z

interesting. perhaps my issues are in part due to me self hosting, i'll deploy it to vercel and monitor the differences

joulev

2024-01-29T15:03:25.000Z

oh yeah it currently seems to be pretty coupled to vercel

you can have it running well for self-host via next start or vercel, but for it to work on other serverless hosts it will take some work at least

Ray

2024-01-29T15:05:17.000Z

yes it works well with self hosting on a node server

Plott HoundOP

2024-01-29T15:05:20.000Z

sorry to go slightly off topic, but since i have you both here - is using unstable_cache with user specific data a bad idea? eg adding the userId to the cache tag. im guessing its a terrible idea especially as the user base grows. is it common to just not cache anything user specific?

eg say i have 10,000 users if each of them have cached data then it would be a performance nightmare

joulev

2024-01-29T15:06:28.000Z

the more you cache the more cost on caching you have to bear

regardless of what you cache

so decide wisely on whether to cache something or not

@Plott Hound eg say i have 10,000 users if each of them have cached data then it would be a performance nightmare

Ray

2024-01-29T15:07:00.000Z

not sure how much it will cost

Plott HoundOP

2024-01-29T15:07:46.000Z

i see. either way the 'performance cost' could outweigh the benefit of caching in the first place

thank you guys, always learning loads from you. have a great day!! â¤ï¸

Ray

2024-01-29T15:08:35.000Z

I think you could not to cache it if the query is fast enought

Plott HoundOP

2024-01-29T15:09:33.000Z

ok. im doing some dashboard stuff where i have lots of 'mini fetches' pushed down to the components that use them which are all suspense wrapped. it seems to work nicely but as always i dont want to be hitting the db more than i need to be

Ray

2024-01-29T15:13:54.000Z

I would cache the user data too if I want to reduce the cost on db.