This is why you need caching 

Keep in mind, this is always dependent on what kind of data you deliver from database. Example1: if you deliver a list of blog posts (which basically a new post appears once/day) .. this is perfect scenario ! But you still have to do update-hooks (for cases where a post was removed; so it does not ghost for another 24h inside the redis cache) Exemple2: if you deliver messages from a roomchat (which basically can change < 1/s depending on how many users there are in the room) .. this is useless to cache. Also, most modern databases already have a caching layer in place. So, IMO , for most use cases , redis is obsolete and just another thing to take care of because adds to project complexity.

I implemented this in my app Cody! When i logged the times using the cache, vs without, it was at least 80 percent faster. Devs like you and Josh Tried Coding are a blessing, teaching us advanced topic to implement in our projects.

Grats on sponsorship!

You do custom thumbnails now! Super interesting topic, thanks for sharing. Got a good experience with upstash as well, very handy for serverless

If you keep this up, you're gonna become the most important tech/eng youtuber out there. No doubt. Keep it up!

I love that you get straight to the point

Insanely helpful man, im definately going to add redis for my saas

heya Cody! this is a good thumbnail for the video! keep up the good work!

Thank you for this great tutorial! I would like to ask how would you handle invalidation or returning the data if there's like pagination involved? Do you set the cache key as the composite of "domainId" + pagination options like limit and page? (eg: post_page1_limit25)

I need to take a look at this. Thanks

redis on a remote server that I need to reach out to every time my api is hit, bugs me. why?

What I don't understand is if cache exists for the user and you return that instead, at what point will they get the latest data if they are only getting the outdated cached data returned?

This is a great video

Good example, thanks

thank you, mate!

love your content... thank you

I used to have Django REST with Redis caching and our Redis was making a copy of its db to a disk. And suddenly we ran out of storage and the API didn't work anymore lol

Hi, I need guidance around what tools and technologies are expected from a 3 years experienced frontend (react.js) developer.

I've a question, why do we need trpc or an end point and not just use prisma client directly on our server component? or do we still need to have an endpoint?

Hi Cody, do you have any ideas how to set the expires' value on the Javscript Fetch calls ?

Is making a local cache manager based on local object or map will be a good idea? Or using redis will be better approach for the best performance?

Hey Cody, are you going to continue the Mantine course platform series?

Will this work this much faster in production also ?

honestly this is seems a bit of an overkill, if you use Redis just to cache for 10 seconds, you have this already built in in the Next framework, those are called `Segment Config Options`. Which you can cache your api request, without any 3rd party providers and without spending more money on them :)(P.S and it will be faster)

Thanks React Query.

This seems less like a reason to use a cache and more of a reason to find out why your query is taking so damn long.

Very nice

Or you could cache the data on disk like a pleb and force everyone working for you to agree even though you just said that the table is going to have 100 rows at most and it's an app used by like 200 people a day max.

Caching is not the answer to poor database schema.

Liked the video still one thing trigged me and that was the else when it was not needed since your if always returns the else would not be needed

I just use redis as my primary db.

Good job babe!!!!

I Don't Understand Why You Wrote false && cache Inside An If Statement You Can Directly Write if(cache) Instead If There Is An Cache Result

[0]