I did not understand the Etag explanation. So If user data is changed by UI the UI will change the etag also so that new data can be stored and refreshed the cache ? Etag is something cache responses in the response.... right ?
Good question! Loading static data into memory instead of using Redis can work for some cases, but there are trade-offs. If the static data is small and rarely changes, keeping it in application memory (like a dictionary or an in-memory cache) is a good idea since it removes the extra network call to Redis. However, if the data is large or updated frequently, Redis stays available across restarts, unlike in-memory storage, and Multiple instances of your app can share the same data without duplicating it in memory. I have made a video on Redis previously, please checkout that in my playlist in description.
that is one of the best tutorial videos on TH-cam that has explained this topic perfectly 👍
There are very few videos out there which explain ETag mechanism. Great video 💯
I did not understand the Etag explanation. So If user data is changed by UI the UI will change the etag also so that new data can be stored and refreshed the cache ? Etag is something cache responses in the response.... right ?
Nice explanation, please make interview asked questions sometimes their questions gets really tricky and OTB
Hey 👋🏻, thanks for all the videos ✨
great quality video, keep up the good work.
Very detailed. Thank you!
excellent video🎉🎉🎉
Awesome video
Why not load static stuff into memory and remove redis dependency?
Good question! Loading static data into memory instead of using Redis can work for some cases, but there are trade-offs. If the static data is small and rarely changes, keeping it in application memory (like a dictionary or an in-memory cache) is a good idea since it removes the extra network call to Redis. However, if the data is large or updated frequently, Redis stays available across restarts, unlike in-memory storage, and Multiple instances of your app can share the same data without duplicating it in memory. I have made a video on Redis previously, please checkout that in my playlist in description.
@@ByteMonk Thank you Mr Monk. You do a great job with your videos.
Josss🎉
In the conditional caching example we are still fetching the data to compare the eTag, how is this improving the bandwidth or efficiency?
If data remains unchanged, only the header is returned without the body which comparatively increases the speed.
Since there is no body being returned, bandwidth utilised will be comparatively less
could you please make a video about how upi is designed and how we can make such a system
Check out my channel home page , it’s already there 🙂
@@ByteMonk I mean the system design of upi network / ncpi network . could you please make a video on that
How you made this animations
👍🏻✨
Bro one request explain microservice plz
I know actually but your animation and visualisation will make concept clear
@ MIcroservices playlist is in my description, enjoy :)