I started a LinkedIn course on Redis, just to see what is it about. After 20 minutes I started to search on TH-cam for a summary of Redis and get the meaning of it in short time. This explanation is short, understandable, just great. Thanks!
I have to admit, I was initially distracted by your glorious beard! :D I have a few questions I hope you can clarify - 1) Why is querying Redis faster than directly querying a database - is it because there is less amount of data to search from? Also, at what point does the cache start removing data? Is the oldest data removed first or is it the data that is accessed least often? 2) If we are using a cache worker to update the Redis cache every time there is a change to the database, why is this any faster than just directly querying the database? It seems that in this case, the Redis cache contains the same amount of information as the database and that the database would be updated before the Redis cache anyways.
Thank you so much. Heard Vercel recently implemented a Key-Value system, and it’s a Redis-like data system. This video gave me a good overview of Redis.
Aha, so basically an in memory cache. Very well structured video; shows the problem and how Redis attempts to solve it, making it intuitive to grasp its purpose.
@Alek Wolf I'm a complete beginner at Redis, but this seems to be a general software problem. Since Redis is an in-memory app that strives to use cache, to decrease the wait time for common data queries, it is based on RAM usage. Since it is based on RAM usage, it's limited by the RAM provided with the machine. I don't think BigData ever was a viable target for usage of Redis. BigData can return huge responses to queries and it's not really feasible to hold it all in limited RAM, a few bigger reports and OOM is achieved. I suppose at that point a better approach would be putting in resources to speed up the access to BigData resources and optimizing queries.
This isn't what redis is, this is just an explanation of how a cache works. Caching is just one use case for redis. This video will make beginners think that redis is a cache, which is false. Redis is an in-memory key-value store with pub-sub model with many use cases such as creating event streams in architecture beyond mere caching.
Sounds interesting 1. What are the memory requirements in the case of a large-scale database to keep this solution effective? 2. How effective this solution for a system that generates random access to a large-scale database? in which case Redis cache would require a lot of memory to stay effective I think that these topics should be referred to by the video.
Hi Shuky, thank you for your questions. It will really depend on the load and amount of data, but there are some profiles in AWS and Azure that will be for enterprise requirements up to 14TB of memory. docs.microsoft.com/en-us/azure/azure-cache-for-redis/cache-planning-faq#azure-cache-for-redis-performance This is a good break down of some performance recommendations. We hope this is helpful! Thank you for learning with us.
Great explanation! wonder what will happen to traffic if the redis goes down? will the web goes down as well as it cant retrieve data from cache? or will the web traffic will go directly to the database. Thanks
Thanks for the great explanation. So in order words, without a cache workers, redis won't be aware of new data and there is always the risk to fetching stale data?
Store data in a redis cache instance and retrieve that data from the RAM of the server that’s running the service. Initially the instance doesn’t have any data instead of it’s config data.
You can check out the course here: www.cbtnuggets.com/it-training/devops/redis-essentials If you're not a current subscriber, you can sign up for a FREE 7-day trial to watch: training.cbt.gg/sbp
So does this mean that the redis caching service will only be a hit if there has already been an existing query on the DB? Also, will the cache itself ever get too full, then what?
I’m not totally clear how the amount of RAM allocated to a docker instance would be able to hold any substantial amount of data from a database. I understand how this is useful for commonly queried data, but wouldn’t the service have to be very selective in what it chooses to cache? And don’t we have to worry about available RAM for the web server? Does Redis ever battle the server for resources?
Well i had a query how long does the redis store a cache for is it for days or hours as if the cache does not clear then the redis cache size would get full right
This isn't what redis is, this is just an explanation of how a cache works. Caching is just one use case for redis. This video will make beginners think that redis is a cache, which is false. Redis is an in-memory key-value store with pub-sub model with many use cases such as creating event streams in architecture beyond mere caching.
So is the preferred pattern to have your webserver do all reads from redis, and all its writes to the database? Then run a cache worker so that the cache gets updated automatically?
This video isn't what redis is, this is just an explanation of how a cache works. Caching is just one use case for redis. This video will make beginners think that redis is a cache, which is false. Redis is an in-memory key-value store with pub-sub model with many use cases such as creating event streams in architecture beyond mere caching. Redis is a tool, like a nail, your preferred pattern in how to use it depends on your architecture which you need to create.
SQL server already has buffer cache where it stores frequently used data from database. This helps in fast data retrieval. How is redis different from SQL Buffer cache ?
My man looks like he's putting tutorials straight from Antarctica
I think he looks pretty similar to Twitter's CEO Jack Dorsey...
This is why indexes were invented, to reduce retrieval time for a query.
Proudly, the 200th like
Damn no I can't take him seriously xD
I started a LinkedIn course on Redis, just to see what is it about. After 20 minutes I started to search on TH-cam for a summary of Redis and get the meaning of it in short time. This explanation is short, understandable, just great. Thanks!
Same here... Linkedin Learning is so verbose and dragged out to increase their minutes...
I thought u were Jack Dorsey at firsts lol
😂 me too
🤣🤣🤣🤣
Me too
lol, me too.
Lmfaooooooooo 😂😂😂
Awesome explanation Trevor. Breaking down problems into dummy understanding is an art.
I have to admit, I was initially distracted by your glorious beard! :D
I have a few questions I hope you can clarify -
1) Why is querying Redis faster than directly querying a database - is it because there is less amount of data to search from? Also, at what point does the cache start removing data? Is the oldest data removed first or is it the data that is accessed least often?
2) If we are using a cache worker to update the Redis cache every time there is a change to the database, why is this any faster than just directly querying the database? It seems that in this case, the Redis cache contains the same amount of information as the database and that the database would be updated before the Redis cache anyways.
Awesome elaboration. He hit the nail straight to the point
Thank you so much. Heard Vercel recently implemented a Key-Value system, and it’s a Redis-like data system. This video gave me a good overview of Redis.
This is a really good video. I’m a network engineer playing with docker and I’ve seen this a few times. Always wondered what it is.
Couldn't have put it better, great work!
FINALLY! a clear explanation as to what it actually does. thank you for this.
Aha, so basically an in memory cache. Very well structured video; shows the problem and how Redis attempts to solve it, making it intuitive to grasp its purpose.
@Alek Wolf I'm a complete beginner at Redis, but this seems to be a general software problem. Since Redis is an in-memory app that strives to use cache, to decrease the wait time for common data queries, it is based on RAM usage. Since it is based on RAM usage, it's limited by the RAM provided with the machine. I don't think BigData ever was a viable target for usage of Redis. BigData can return huge responses to queries and it's not really feasible to hold it all in limited RAM, a few bigger reports and OOM is achieved. I suppose at that point a better approach would be putting in resources to speed up the access to BigData resources and optimizing queries.
This isn't what redis is, this is just an explanation of how a cache works. Caching is just one use case for redis. This video will make beginners think that redis is a cache, which is false. Redis is an in-memory key-value store with pub-sub model with many use cases such as creating event streams in architecture beyond mere caching.
awesome explanation and greatly clear english speaking. I can fully listen to you without looking at the sub. Well done!
Thanks for starting from User experience, so we can understand the use-case clearly.
That's a nice explanation Trevor, i like the way you explained bit by bit to understanding level
Very good in explaining Redis serving as a cache system; would be nice to expand to all important features of Redis ...
What if the user has updated he is info, Would the user get an old data or new data?
Awesome dude... simple and crispy explanation. Keep it up appreciate.
simple and clear, to the point.......really like the way you explain.
i agree with your thinking！🥤cheers🥤
You did such a great job explaining this, thank you.
real quick and awesomely covered in less time.
Nice video Sir ,please carry on ,nice voice clarity and representation
Simple and precise, it made me recall how my fried explained me about Redis and Guava caching but unfortunately i dont recall the difference btw them.
Sounds interesting
1. What are the memory requirements in the case of a large-scale database to keep this solution effective?
2. How effective this solution for a system that generates random access to a large-scale database?
in which case Redis cache would require a lot of memory to stay effective
I think that these topics should be referred to by the video.
Hi Shuky, thank you for your questions.
It will really depend on the load and amount of data, but there are some profiles in AWS and Azure that will be for enterprise requirements up to 14TB of memory. docs.microsoft.com/en-us/azure/azure-cache-for-redis/cache-planning-faq#azure-cache-for-redis-performance This is a good break down of some performance recommendations.
We hope this is helpful! Thank you for learning with us.
thank you, it was so helpful
I like the way you explain things, please keep going 👍
Great explanation! wonder what will happen to traffic if the redis goes down? will the web goes down as well as it cant retrieve data from cache? or will the web traffic will go directly to the database. Thanks
Thank you for the explanation, you made it simple to understand.
Thanks for the great explanation. So in order words, without a cache workers, redis won't be aware of new data and there is always the risk to fetching stale data?
Best video on Redis ❤️
Liking for the adorable outro. It HAS been informative for me!
Wish we all Had Guys like this before College.
Redis, which stands for Remote Dictionary Server cements it
Store data in a redis cache instance and retrieve that data from the RAM of the server that’s running the service.
Initially the instance doesn’t have any data instead of it’s config data.
Awesome explanation in easy way ❤
Redis In-Memory database ! Redis Cache Service ! .... mmm... interesting.
awesome explanation jack dorsey
This was very helpful. Thanks sir!
We're so glad it's helpful for you! Thank you for learning with us.
Thank you. It cleared all my doubts😀
Excellent video! Thanks a lot.
Many thanks for the explanation
very clear explanation. make us impressed a lot.
Thank you so much! That was very informative! I learned the scenarios of how I can use Redis.
Thank you for your great explanation! 💥
Clean and clear. Thank you very much!
Very well explained. Thanks
is there a follow up on this, or is this part of some series that is available elsewhere? Thanks in advance!
You can check out the course here: www.cbtnuggets.com/it-training/devops/redis-essentials
If you're not a current subscriber, you can sign up for a FREE 7-day trial to watch: training.cbt.gg/sbp
@@cbtnuggets Thank you very much!
Excellent explanation, thanks a lot 🤗
So does this mean that the redis caching service will only be a hit if there has already been an existing query on the DB?
Also, will the cache itself ever get too full, then what?
thank you for such a quick useful explanation
01:20 the query wont take 30s if made by a user since its most of the time OLTP
Hi Trevor Sullivan
Truly a great beard, so wow! much wisdom!
Wonderful Video! Thank you for the clear explanation!
Just what I needed.
So why not do the caching at server/api level ?
That was really helpful...Thank You!!
Very good explanation.
I read somewhere redis is a great use case for chat apps. How does that be inline with caching I am very confused
Can you please let us know how the Redis implementation in Openstack Controller works?
Thanks, that was very helpful.
Very informative. Thank you.
Excellent explanation!!!
I’m not totally clear how the amount of RAM allocated to a docker instance would be able to hold any substantial amount of data from a database. I understand how this is useful for commonly queried data, but wouldn’t the service have to be very selective in what it chooses to cache? And don’t we have to worry about available RAM for the web server? Does Redis ever battle the server for resources?
excellent explanation
Good for start. Thanks 😊
Why do we need database when we can store everything in redis in the first place?
awesome. simple and explained with diagrams !
That was a great breakdown thanks!!!
where is the next video ? i cant find it
Fantastic! concise. clear
excellent explanation!
I see no one is make it, so I'll do.
You know extension of redis name?
Redis what?
Redis nutz
Great video all in all, thanks for the explanation.
awesome loved it!!!!
Well i had a query how long does the redis store a cache for is it for days or hours as if the cache does not clear then the redis cache size would get full right
Thank you for this content. very helpful
save your self the trouble and just use redis as a database, it is amazing
Cache hit on the explanation
This isn't what redis is, this is just an explanation of how a cache works. Caching is just one use case for redis. This video will make beginners think that redis is a cache, which is false. Redis is an in-memory key-value store with pub-sub model with many use cases such as creating event streams in architecture beyond mere caching.
good explanation. thakns a bunch
Hi, can you please do a video on Ncache?
Request here! www.cbtnuggets.com/request-training
thanks for creating this video,
very informative. thanks gistalot
Wonderful tutorial, thank you.
thanks, very well explained and clear
Well understood 😎. Thanks
So is the preferred pattern to have your webserver do all reads from redis, and all its writes to the database? Then run a cache worker so that the cache gets updated automatically?
This video isn't what redis is, this is just an explanation of how a cache works. Caching is just one use case for redis. This video will make beginners think that redis is a cache, which is false. Redis is an in-memory key-value store with pub-sub model with many use cases such as creating event streams in architecture beyond mere caching. Redis is a tool, like a nail, your preferred pattern in how to use it depends on your architecture which you need to create.
Very informative.
Great explanation thanks.
Great video!
Thank you
Greatly explained
Thankyou
Thanks! Helped me alott!!
SQL server already has buffer cache where it stores frequently used data from database. This helps in fast data retrieval.
How is redis different from SQL Buffer cache ?
If using sql then i think no need to use redis
Well explained
I used to hit the cache pretty hard in college.
Thank you for this
why always introduce ? is it impotant?
I mean I guess this cache is only good if the data is quite small or we always request thr same data
Amazing content, tkss
Trade off made from correctness of retrieved value hence it is a cache…