I started a LinkedIn course on Redis, just to see what is it about. After 20 minutes I started to search on KZbin for a summary of Redis and get the meaning of it in short time. This explanation is short, understandable, just great. Thanks!
@pinxtr3 жыл бұрын
My man looks like he's putting tutorials straight from Antarctica
@opossum44633 жыл бұрын
He looks like the CEO of a certain fortune 500 company. And that can't be a bad thing.
@opossum44633 жыл бұрын
I mean, minus the nose ring.
@codepractices73 жыл бұрын
I think he looks pretty similar to Twitter's CEO Jack Dorsey...
@kw199915 ай бұрын
This is why indexes were invented, to reduce retrieval time for a query.
@h456-m1l15 күн бұрын
Proudly, the 200th like
@riskitall74212 жыл бұрын
Awesome explanation Trevor. Breaking down problems into dummy understanding is an art.
@ekanastone3 жыл бұрын
I thought u were Jack Dorsey at firsts lol
@hangout70813 жыл бұрын
😂 me too
@musaopaluwa25802 жыл бұрын
🤣🤣🤣🤣
@mdbasaz2 жыл бұрын
Me too
@akeinchina2 жыл бұрын
lol, me too.
@user-td5gy2fh3p11 ай бұрын
Lmfaooooooooo 😂😂😂
@courageahorttor76663 жыл бұрын
Awesome elaboration. He hit the nail straight to the point
@Paul_Aderoju Жыл бұрын
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.
@PowerUsr12 жыл бұрын
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.
@StrikerEureka852 жыл бұрын
FINALLY! a clear explanation as to what it actually does. thank you for this.
@kaushikdr3 жыл бұрын
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.
@ThefamousMrcroissant2 жыл бұрын
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.
@deedoodeedoo63822 жыл бұрын
@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.
@adityamittal43572 жыл бұрын
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.
@didorins4994 Жыл бұрын
Thanks for starting from User experience, so we can understand the use-case clearly.
@RedisUniversity3 жыл бұрын
Couldn't have put it better, great work!
@MrPx07272 жыл бұрын
Very good in explaining Redis serving as a cache system; would be nice to expand to all important features of Redis ...
@davidmunyiri614711 ай бұрын
That's a nice explanation Trevor, i like the way you explained bit by bit to understanding level
@mohammadzulqarnain62883 жыл бұрын
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.
@lil_soumАй бұрын
You did such a great job explaining this, thank you.
@osmangani49663 жыл бұрын
simple and clear, to the point.......really like the way you explain.
@jackcastro95832 жыл бұрын
i agree with your thinking!🥤cheers🥤
@bsummer2 жыл бұрын
Wish we all Had Guys like this before College. Redis, which stands for Remote Dictionary Server cements it
@baolam41802 жыл бұрын
awesome explanation and greatly clear english speaking. I can fully listen to you without looking at the sub. Well done!
@Food.5inder Жыл бұрын
Awesome dude... simple and crispy explanation. Keep it up appreciate.
@Shubham__Saroj2 жыл бұрын
real quick and awesomely covered in less time.
@kunalb20513 жыл бұрын
Best video on Redis ❤️
@Kirimoshi4 ай бұрын
I like the way you explain things, please keep going 👍
@RoshanakRahimi-d1p Жыл бұрын
thank you, it was so helpful
@kinax23 жыл бұрын
What if the user has updated he is info, Would the user get an old data or new data?
@ans42101 Жыл бұрын
Thank you for the explanation, you made it simple to understand.
@abbasabdulsalambamidele87602 ай бұрын
Very well explained. Thanks
@Acumen9283 жыл бұрын
Just what I needed.
@mirishfaqhussain93022 жыл бұрын
awesome explanation jack dorsey
@vop0092 Жыл бұрын
Awesome explanation in easy way ❤
@rupeshsingh36072 жыл бұрын
Nice video Sir ,please carry on ,nice voice clarity and representation
@gagang.r684 Жыл бұрын
Thank you. It cleared all my doubts😀
@VishalSharma-k7b Жыл бұрын
Clean and clear. Thank you very much!
@aparnasaha97297 ай бұрын
excellent explanation
@ann_uken Жыл бұрын
Thank you for your great explanation! 💥
@renyirish9 ай бұрын
Excellent explanation, thanks a lot 🤗
@torrvic11564 ай бұрын
Thank you so much! That was very informative! I learned the scenarios of how I can use Redis.
@darrenklein6090 Жыл бұрын
Thanks, that was very helpful.
@Joop503710 ай бұрын
Very good explanation.
@rednejiv1233 жыл бұрын
Excellent video! Thanks a lot.
@Banjer10 ай бұрын
Excellent explanation!!!
@koders97783 жыл бұрын
This was very helpful. Thanks sir!
@cbtnuggets3 жыл бұрын
We're so glad it's helpful for you! Thank you for learning with us.
@BlueDolphinBlues5 ай бұрын
Hi Trevor Sullivan
@ShukyPersky3 жыл бұрын
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.
@cbtnuggets3 жыл бұрын
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.
@indrranil24 Жыл бұрын
awesome loved it!!!!
@姚瑶-q8w2 жыл бұрын
very clear explanation. make us impressed a lot.
@chriskaye19972 жыл бұрын
Truly a great beard, so wow! much wisdom!
@juejuepaing69852 жыл бұрын
Thank you
@adamdymurski9342 Жыл бұрын
Good for start. Thanks 😊
@tylercode2207 Жыл бұрын
That was really helpful...Thank You!!
@briarsmith8241 Жыл бұрын
Cache hit on the explanation
@krishnashah66546 ай бұрын
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.
@BassZeke3 жыл бұрын
Fantastic! concise. clear
@IchEsseKonsolen3 жыл бұрын
Liking for the adorable outro. It HAS been informative for me!
@canyoldas2855 Жыл бұрын
Very informative. Thank you.
@rehamalbulushi5202 жыл бұрын
thank you for such a quick useful explanation
@workpfeiffer34282 жыл бұрын
good explanation. thakns a bunch
@martinkarkovich30373 жыл бұрын
excellent explanation!
@DebbieGOfficial Жыл бұрын
Well explained
@Ibrahim-oc5qlАй бұрын
very informative. thanks gistalot
@none0n Жыл бұрын
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?
@rahimeinollahi12 жыл бұрын
thanks for creating this video,
@globalclutter95083 жыл бұрын
Very informative.
@mikkeljensen1603 Жыл бұрын
save your self the trouble and just use redis as a database, it is amazing
@diet92 Жыл бұрын
Well understood 😎. Thanks
@hackcodesfree9200 Жыл бұрын
super explained
@shadymilkman102 жыл бұрын
That was a great breakdown thanks!!!
@niponchanda83562 жыл бұрын
Greatly explained
@stevendaddario88032 жыл бұрын
Wonderful Video! Thank you for the clear explanation!
@shantanu1432 жыл бұрын
awesome. simple and explained with diagrams !
@xtianseyer0182 жыл бұрын
Thank you for this
@edwardfraser6883 жыл бұрын
Great explanation thanks.
@juneldomingo62772 жыл бұрын
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
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.
@shalinijaiswal57182 жыл бұрын
insightful
@salahalhashmi65283 жыл бұрын
thanks
@MatichekYoutube9 ай бұрын
thanks, ..
@ranjeetbadhe Жыл бұрын
Can you please let us know how the Redis implementation in Openstack Controller works?
@whatthefunction91403 жыл бұрын
Hi Trev
@LooneyTunesCarrot3210 ай бұрын
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?
@i3looi23 ай бұрын
So why not do the caching at server/api level ?
@vishalk27983 жыл бұрын
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