What is Redis and What Does It Do?

[@pinxtr]

My man looks like he's putting tutorials straight from Antarctica

[@opossum4463]

He looks like the CEO of a certain fortune 500 company. And that can't be a bad thing.

[@opossum4463]

I mean, minus the nose ring.

[@samarth319]

I think he looks pretty similar to Twitter's CEO Jack Dorsey...

[@kw19991]

This is why indexes were invented, to reduce retrieval time for a query.

[@lajos108]

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!

[@riskitall7421]

Awesome explanation Trevor. Breaking down problems into dummy understanding is an art.

[@ekanastone]

I thought u were Jack Dorsey at firsts lol

[@hangout7081]

😂 me too

[@musaopaluwa2580]

🤣🤣🤣🤣

[@mdbasaz]

Me too

[@akeinchina]

lol, me too.

[@user-td5gy2fh3p]

Lmfaooooooooo 😂😂😂

[@courageahorttor7666]

Awesome elaboration. He hit the nail straight to the point

[@ThefamousMrcroissant]

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.

[@deedoodeedoo6382]

@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.

[@adityamittal4357]

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.

[@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.

[@RedisUniversity]

Couldn't have put it better, great work!

[@PowerUsr1]

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.

[@StrikerEureka85]

FINALLY! a clear explanation as to what it actually does. thank you for this.

[@didorins4994]

Thanks for starting from User experience, so we can understand the use-case clearly.

[@kaushikdr]

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.

[@osmangani4966]

simple and clear, to the point.......really like the way you explain.

[@jackcastro9583]

i agree with your thinking！🥤cheers🥤

[@MrPx0727]

Very good in explaining Redis serving as a cache system; would be nice to expand to all important features of Redis ...

[@Kirimoshi]

I like the way you explain things, please keep going 👍

[@davidmunyiri6147]

That's a nice explanation Trevor, i like the way you explained bit by bit to understanding level

[@kunalb2051]

Best video on Redis ❤️

[@Shubham__Saroj]

real quick and awesomely covered in less time.

[@xxxxxGhostBoyxxxxx]

the beard is an indicator of experience

[@baolam4180]

awesome explanation and greatly clear english speaking. I can fully listen to you without looking at the sub. Well done!

[@krishnashah6654]

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.

[@user-rj8yv5nz3f]

thank you, it was so helpful

[@Food.5inder]

Awesome dude... simple and crispy explanation. Keep it up appreciate.

[@torrvic1156]

Thank you so much! That was very informative! I learned the scenarios of how I can use Redis.

[@Acumen928]

Just what I needed.

[@Joop5037]

Very good explanation.

[@kinax2]

What if the user has updated he is info, Would the user get an old data or new data?

[@mohammadzulqarnain6288]

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.

[@ShukyPersky]

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.

[@cbtnuggets]

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.

[@ans42101]

Thank you for the explanation, you made it simple to understand.

[@IchEsseKonsolen]

Liking for the adorable outro. It HAS been informative for me!

[@aparnasaha9729]

excellent explanation

[@koders9778]

This was very helpful. Thanks sir!

[@cbtnuggets]

We're so glad it's helpful for you! Thank you for learning with us.

[@juejuepaing6985]

Thank you

[@bsummer]

Wish we all Had Guys like this before College. Redis, which stands for Remote Dictionary Server cements it

[@rednejiv123]

Excellent video! Thanks a lot.

[@BlueDolphinBlues]

Hi Trevor Sullivan

[@vop0092]

Awesome explanation in easy way ❤

[@user-cw9vj4sl5l]

Clean and clear. Thank you very much!

[@rupeshsingh3607]

Nice video Sir ,please carry on ,nice voice clarity and representation

[@mirishfaqhussain9302]

awesome explanation jack dorsey

[@user-xx2td2mf6b]

very clear explanation. make us impressed a lot.

[@BassZeke]

Fantastic! concise. clear

[@renyirish]

Excellent explanation, thanks a lot 🤗

[@Banjer]

Excellent explanation!!!

[@rehamalbulushi520]

thank you for such a quick useful explanation

[@sandhyakaranam6113]

great explanation , thank you

[@briarsmith8241]

Cache hit on the explanation

[@ann_uken]

Thank you for your great explanation! 💥

[@gagang.r684]

Thank you. It cleared all my doubts😀

[@juneldomingo6277]

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

[@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?

[@lovinthumper]

Very informative.

[@darrenklein6090]

Thanks, that was very helpful.

[@martinkarkovich3037]

excellent explanation!

[@chriskaye1997]

Truly a great beard, so wow! much wisdom!

[@DebbieGOfficial]

Well explained

[@adamdymurski9342]

Good for start. Thanks 😊

[@mikkeljensen1603]

save your self the trouble and just use redis as a database, it is amazing

[@stevendaddario8803]

Wonderful Video! Thank you for the clear explanation!

[@androidsavior]

where is the next video ? i cant find it

[@shantanu143]

awesome. simple and explained with diagrams !

[@i3looi2]

So why not do the caching at server/api level ?

[@canyoldas2855]

Very informative. Thank you.

[@LooneyTunesCarrot32]

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?

[@amanuelyohannes7151]

I read somewhere redis is a great use case for chat apps. How does that be inline with caching I am very confused

[@edwardfraser688]

Great explanation thanks.

[@williamfriedeman7078]

Wonderful tutorial, thank you.

[@shadymilkman10]

That was a great breakdown thanks!!!

[@aakarshanraj1176]

01:20 the query wont take 30s if made by a user since its most of the time OLTP

[@hackcodesfree9200]

super explained

[@rahimeinollahi1]

thanks for creating this video,

[@niponchanda8356]

Greatly explained

[@francoisbourdages2906]

thanks, very well explained and clear

[@tylercode2207]

That was really helpful...Thank You!!

[@frogman3107]

Why do we need database when we can store everything in redis in the first place?

[@mazdanaqvy3754]

Thanks

[@indrranil24]

awesome loved it!!!!

[@rasnacv3802]

Thank you for this content. very helpful

[@nicklowe_]

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?

[@ranjeetbadhe]

Can you please let us know how the Redis implementation in Openstack Controller works?

[@ns4k_tv]

Thanks! Helped me alott!!

[@duartelucas5746]

is there a follow up on this, or is this part of some series that is available elsewhere? Thanks in advance!

[@cbtnuggets]

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

[@duartelucas5746]

@@cbtnuggets Thank you very much!

[@TANRININresulu]

Trade off made from correctness of retrieved value hence it is a cache…

[@adityamittal4357]

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.

[@muhammedmusharaf386]

Thankyou

[@workpfeiffer3428]

good explanation. thakns a bunch

[@diet92]

Well understood 😎. Thanks

[@whatthefunction9140]

I used to hit the cache pretty hard in college.

[@xtianseyer018]

Thank you for this

[@MatichekYoutube]

thanks, ..

[@vishalk2798]

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

[@Ferruccio_Guicciardi]

Redis In-Memory database ! Redis Cache Service ! .... mmm... interesting.

[@zmark2274]

That easy, thank you

[@quirkyquester]

Great video!

[@brighteragyemang8765]

Thank you!

[@jordanpedroinvestimentos]

Good video

[@sangtengkorak1954]

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.

[@leedy8135]

why always introduce ? is it impotant?

[@UmairKhan-xz2df]

Hi, can you please do a video on Ncache?

[@cbtnuggets]

Request here! www.cbtnuggets.com/request-training