Josh, thanks for the video... can you please explain in the next video... how can we use this in production? and how can we sync the redis with our sql or mongo db?
Very good video, I congratulate you. I ask you a question, suppose I have an application with a mysql database, my app calls an api to query and show products to the user, if I implement you Redis to cache the busquedaby that the api first see if you have stored in cache and if not just then go to query the database, with the first user who enters the app Eedis stored in the server cache and then if another user comes and asks to see the products would be set in that cache even if they are different users? The cache has a time and then it is deleted and the search to the database is done again, right? Thank you very much
Excelent video Josh! I was wondering in which cases would you use redis instead of an actual database? Since the latest is way more powerfull and cheep, is there some edge cases where using redis would be better? I can't stop comparing the 10k comments / day from upstash against the 1billon read from Planetscale 🤔 Thanks for all the content :) It really helps a lot
For the past 2 weeks I been learning redis through docs and now you droped this gem 💎 You are the most consistent youtuber with such high quality content. Thank you for this tutorial I wish this was 4-5+ hr long
Bro, can you make a tutorial on migrating express server to next js or at the very least use express server together with next js, I would greatly appreciate
Needs some real world examples and applications in the video. I think people use redis mostly for rate limiting and session storage? Or would anyone seriously pick redis for saving userdata over a sql db?
I think it would have been better to create the three tags under tags: etc and you then have a set or list inside the comment linking the the id of one specific tag
How would you cache a list of data like posts? In reality, wouldnt this be more practical than just a caching a single post since it would take longer to fetch. Could I just a set a dummy key like "posts" and store value there? And whenever new post is added, or existing post is edited/deleted, would have to flush
What would the performance benefits be to using Redis JSON to just store, say, a cached API response as opposed to just stringifying/parsing the standard Redis string response? The JSON has to be marshaled anyways by ioredis. My current use cases don't involve granular edits to nested data. I just store and retrieve the whole thing.
Great video, but kinda funny how you ended it by practically saying "nothing I showed you is how people normally use redis" and then just ended the video... lol
Thanks man. I think you kinda missed the point. The point of the video is to learn when to use redis and which data types for which purpose. The transfer of applying that knowledge to a database call is non-existent. You get the result and put it into redis just the same way you learn in the video. You could even argue the comment data object was a database result, just mocked
Keeping track of all comment ids in a list makes sense to easily fetch the x latest comments. With those IDs, you can go ahead and fetch the details for each comment - because the key you store those as is defined by the commentId (e.g. comment_details:commentId). No need to keep track of it separately
Another important key type is Streams. I find it useful for multiplayer games and chat apps were the data needs to be streamed in and updates subscribed to. It's like a little Kafka.
Really nice video on a interesting topic! In the introduction you say you would explain 'when' to use redis but I'm not sure I got it. Would have been great to explain when to use redis over SQL for example.
Throughout the video and at the end I mention the role many people use it as - a cache for your mysql / postgres / mongo database. Not only does it take load off of the primary db, but also speeds up requests for frequently requested resources. Hope that helps!
I know Upstash sponser you, but I'm sure many people watching are not interested in them. It feels a bit like your making this tutorial not to teach us Redis, but to plug Upstash in a video
Unfortunate you feel this way. The API is basically the same, that's why I show the whole express / any framework of your choice setup as well. It doesn't matter how you follow along, the focus is on Redis and not on the underlying provider
Hey ddue! Not sure what you mean by library.. I just write all the stuff in there for the videos and use icons from flaticon. I don't use a paid version for excalidraw. Cheers man
Just at 18:00 min of thr video Im loking most so far but one thing. Why use next.js to teach a new stack? Sigh nextJS already has its unique caveats l, it would have been better seen the setup in plain front/backends like a node/express backend and a vite fromt end, that way we learn how to set it up in general and then addpated to whatever framework we want to use (next, solid, svektekit, etc) show was the most pure form first 😔
Fair point. That's why I showed how to set up a locally hosted Redis in the beginning, so you can easily follow along in any other framework/language. I'd used ioredis to connect to it, but there are a bunch of clients to connect to locally hosted Redis. The API is close to the same, just wanted to also show Redis for serverless environments because not a lot of existing videos do that.
Just in time I plan to build my next app with upstash! Great Content!
Cheers man, looking forward to it!
Waiting for your content also
Josh, thanks for the video... can you please explain in the next video... how can we use this in production?
and how can we sync the redis with our sql or mongo db?
Thanks. About JSON was interesting.
Very good video, I congratulate you. I ask you a question, suppose I have an application with a mysql database, my app calls an api to query and show products to the user, if I implement you Redis to cache the busquedaby that the api first see if you have stored in cache and if not just then go to query the database, with the first user who enters the app Eedis stored in the server cache and then if another user comes and asks to see the products would be set in that cache even if they are different users? The cache has a time and then it is deleted and the search to the database is done again, right? Thank you very much
Thansk for the awesome content man
Cheers!
give your slide about redis pls
Wondering if it will work or not if we do something like this.
redis.json.set('key', '$.tags.TypeScript', true)
time: 34:06
i like your videos, but you mix evry topic with nextjs 🙃
Same feedback 😮💨😢. I love the content but I just wish the were more generic so I can use it in not nextjs (I prefer to use vite) but even svelte.
First :))
cheers dude haha
These crash courses over fundamental topics are a blessing, helps me with my own projects
Fantastic tutorial Josh. Can you please make such crash courses on other topics like React Query, tRPC etc ?
Excelent video Josh!
I was wondering in which cases would you use redis instead of an actual database? Since the latest is way more powerfull and cheep, is there some edge cases where using redis would be better?
I can't stop comparing the 10k comments / day from upstash against the 1billon read from Planetscale 🤔
Thanks for all the content :) It really helps a lot
Great video!
I'd be interested in a follow up for using redis as a cache and then syncing it with a real MySQL database.
For the past 2 weeks I been learning redis through docs and now you droped this gem 💎
You are the most consistent youtuber with such high quality content. Thank you for this tutorial
I wish this was 4-5+ hr long
I think there is Stephen Griders course on Udemy that is over 9hrs long on the redis topic..
Really appreciate that man. Means a lot.
Ohhh hiii Josh, thanks for the redis course, I was making a stackoverflow clone and needed this very much !
cheers dude happy to hear that. Appreciate you commenting so regularly
@@joshtriedcoding thank you josh for noticing comments, is really took years to find a teacher (guru in India)
Bro, can you make a tutorial on migrating express server to next js or at the very least use express server together with next js, I would greatly appreciate
thanks bro
can I know the canvas tool is been used?
redis doesnt come with the json integration, showing us the installation of this would be helpful.
I thought Redis was for ephemeral data?
As nextjs already caches request, do we still need it?
Needs some real world examples and applications in the video. I think people use redis mostly for rate limiting and session storage? Or would anyone seriously pick redis for saving userdata over a sql db?
You missed the most important feature! Guess what it is…😊
how to use zrem using uptash redis
You did not mention TTL!
Another one! Thanks Josh
Youre welcome man. Appreciate ya
ty
Yooo, I literally setup upstash/redis in my project yesterday!
I think it would have been better to create the three tags under tags: etc and you then have a set or list inside the comment linking the the id of one specific tag
How would you cache a list of data like posts? In reality, wouldnt this be more practical than just a caching a single post since it would take longer to fetch.
Could I just a set a dummy key like "posts" and store value there? And whenever new post is added, or existing post is edited/deleted, would have to flush
What would the performance benefits be to using Redis JSON to just store, say, a cached API response as opposed to just stringifying/parsing the standard Redis string response? The JSON has to be marshaled anyways by ioredis. My current use cases don't involve granular edits to nested data. I just store and retrieve the whole thing.
i prefer to use docker instead of using virtualization in my machine it's more flexible. great video btw
Third Comment :))
It won't be wrong if I say that Upstash sponsored Josh's whole career for now 🤣🤣
Talk about KeyDB, it has enterprise features of redis
Bro, you're the best, I freaking love u dude
awesome!
I am subscribing to this channel
You did it. tks a lot
Great cover - thank you!
All concise, and right to the point. Great job, Josh. God bless
Josh🙏🇨🇲
Ein ganz kurzer Kurs, der doch sehr gründlich ist!
Also kurz gesagt: toller Kurs!
Great video, but kinda funny how you ended it by practically saying "nothing I showed you is how people normally use redis" and then just ended the video... lol
Thanks man. I think you kinda missed the point. The point of the video is to learn when to use redis and which data types for which purpose. The transfer of applying that knowledge to a database call is non-existent. You get the result and put it into redis just the same way you learn in the video. You could even argue the comment data object was a database result, just mocked
Great video. Any reason why you didn’t store the commentId inside the JSON object. Why did you keep them seperate?
Keeping track of all comment ids in a list makes sense to easily fetch the x latest comments. With those IDs, you can go ahead and fetch the details for each comment - because the key you store those as is defined by the commentId (e.g. comment_details:commentId). No need to keep track of it separately
Another important key type is Streams. I find it useful for multiplayer games and chat apps were the data needs to be streamed in and updates subscribed to. It's like a little Kafka.
True. I used it in online trading app. It's lightweight, fast, and easy to use
a question...
In the end Redis saves everything as a strig..
So what is the difference between this and just doing
JSON.stringify()
??
Why installing wsl may be docker is easy to setup but I m not sure how it works on windows
docker desktop
redis is just soo good
really like it too
But what about react-query? Is it having a similar use case?
redis and react query are two very different things
Really nice video on a interesting topic!
In the introduction you say you would explain 'when' to use redis but I'm not sure I got it. Would have been great to explain when to use redis over SQL for example.
Throughout the video and at the end I mention the role many people use it as - a cache for your mysql / postgres / mongo database. Not only does it take load off of the primary db, but also speeds up requests for frequently requested resources. Hope that helps!
@@joshtriedcoding thanks
Keep it going champ, you doing it great!
so are you man, cheers
Likes at 18:41, 404
Its pm not video timing
I know Upstash sponser you, but I'm sure many people watching are not interested in them. It feels a bit like your making this tutorial not to teach us Redis, but to plug Upstash in a video
Unfortunate you feel this way. The API is basically the same, that's why I show the whole express / any framework of your choice setup as well. It doesn't matter how you follow along, the focus is on Redis and not on the underlying provider
Upstash is NOT Redis! You're misleading people.
Hey Josh! What's in your Excelifraw Library? Also, Do you use Excelidraw+?
Hey ddue! Not sure what you mean by library.. I just write all the stuff in there for the videos and use icons from flaticon. I don't use a paid version for excalidraw. Cheers man
@@joshtriedcoding Well the top right button....
@@mohakbajaj4235 oh, it just says "no items added yet"
Just at 18:00 min of thr video Im loking most so far but one thing. Why use next.js to teach a new stack? Sigh nextJS already has its unique caveats l, it would have been better seen the setup in plain front/backends like a node/express backend and a vite fromt end, that way we learn how to set it up in general and then addpated to whatever framework we want to use (next, solid, svektekit, etc) show was the most pure form first 😔
Fair point. That's why I showed how to set up a locally hosted Redis in the beginning, so you can easily follow along in any other framework/language. I'd used ioredis to connect to it, but there are a bunch of clients to connect to locally hosted Redis. The API is close to the same, just wanted to also show Redis for serverless environments because not a lot of existing videos do that.