Комментарии:
Will this work this much faster in production also ?
ОтветитьCaching is not the answer to poor database schema.
Ответить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.
ОтветитьInsanely helpful man, im definately going to add redis for my saas
ОтветитьHi, I need guidance around what tools and technologies are expected from a 3 years experienced frontend (react.js) developer.
Ответить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?
ОтветитьI need to take a look at this. Thanks
ОтветитьI love that you get straight to the point
Ответить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)
Hi Cody, do you have any ideas how to set the expires' value on the Javscript Fetch calls ?
Ответитьheya Cody! this is a good thumbnail for the video! keep up the good work! <3
Ответить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
ОтветитьHey Cody, are you going to continue the Mantine course platform series?
Ответить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.
Ответить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?
Ответитьlove your content... thank you
ОтветитьI just use redis as my primary db.
ОтветитьVery nice
Ответить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?
Ответить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
Ответить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.
ОтветитьGrats on sponsorship! <3
ОтветитьGood job babe!!!!
Ответить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)
ОтветитьYou do custom thumbnails now! Super interesting topic, thanks for sharing. Got a good experience with upstash as well, very handy for serverless
Ответить[0]
Ответить