I always hated Indian accent, but after listening to about a 100 videos by some really smart indians explained in a very humble manner..... I really appreciate this accent. Take a very difficult concept to explain and ask an Indian to explain it in English keeping their accent. The emphasis on many words give your time to relax and take in the concepts at the right pace
Very worth & neat session! Keep it up! I have a question ,can you explain how data stored in cache. key- Request value- Response key and value as a Map? can we use concurrentHashMap rather than LinkedHashMap.
Thanks. That's right. Data is mainly stored in key, value form in cache. Actually cache is implemented using Linked list & Hashing. So concurrentHashMap doesn't look ideal Data structure for it. I've explained cache implementation in Queue playlist. If you're interested, please see that video which'll help in understanding it. Thanks.
@@CodingSimplified in my opinion concurrenthashmap looks good when you want to have thread safety + decent performance. If in interview you are asked so then CHMP can solve some of your problems like concurrency, no race condition, efficient locking (bucket level), thread safety, better performance and scalable. Agree?
Write back cache is protected using RAID levels usually now a days RAID 6 or 1and media is SSD. On the other hand cache through SSD along with RAID level directly on the IO module is most efficient but cotly process.
Great tutorial but what are you talking "you have multiple servers on a website". It's not correct. A website has multiple servers. And again " servers are hitting on the webserver" what does that mean? Do you mean "Requests are hitting on the webserver"?
Hi, Thanks for the video, I have a question. While in the write around caching mechanism, it says it stores bypassing cache, directly into db. When it tries to load data, it makes cache miss then it gets data from db and then re-insult to cache. My question here is, what if there was an existing cache, and make write-around method when writing that data. Then data will be affected in database, but it will not be affected in cache. What if we try to load that data again, then there will be that data in cache, and load old cache data. Is this a disadvantage of write around cache? I thought that caching mechanisms only deal with latency for the load, so this case should not happen. Please let me know if anything I'm missing from this concept. Thanks!
Hi, thanks for liking the video. Here our concept is about Cache Invalidation, which means we want to update cache with data. Now if we'll use old cache & showing old data, we're defeating our purpose. We need to show latest data, that's reason we can't use old cache here. I hope it answers your question.
Hi, I belive that there is client(front end) & server(backend). Server means always backend. Say in case of web browser which is initiated from front end(client) & request is sent to backend (server). My doubt is - is there something like front end server also? When u say web server, is it front end or backend? Can caching be done in front end/client side also without sending the request to server?
- when we say client, it means user, Now server can be at front end (UI) & at backend (API server) - Caching can be done at front end as well on back end. Let me know if you've any further questions.
It depends on size of cache. As far as cache size is not full, there is no time limit. It can stay for longer duration. Data will be out from cache: If you flush cache or cache size limit is reached & least recently data is evicted
Great content, really informative. It's just amazing how you can say "applications" perfectly with a proper 'S' at the end, but you say "shtore" instead of "store", surely you can pronounce the sound 'S'....
I am really thankful to you that you made this playlist
Thanks
I always hated Indian accent, but after listening to about a 100 videos by some really smart indians explained in a very humble manner..... I really appreciate this accent.
Take a very difficult concept to explain and ask an Indian to explain it in English keeping their accent. The emphasis on many words give your time to relax and take in the concepts at the right pace
Thanks Amal for your nice feedback. Keep Watching.
It's pronounced as in "CASH"
Well defined session
Thanks for your nice feedback. Keep Watching.
Worth to watch
Thanks for nice feedback. Keep Watching :)
Thanks man. poweful videos
Thanks for nice feedback. Keep Watching :)
Very worth & neat session! Keep it up!
I have a question ,can you explain how data stored in cache.
key- Request
value- Response
key and value as a Map? can we use concurrentHashMap rather than LinkedHashMap.
Thanks. That's right. Data is mainly stored in key, value form in cache. Actually cache is implemented using Linked list & Hashing. So concurrentHashMap doesn't look ideal Data structure for it. I've explained cache implementation in Queue playlist. If you're interested, please see that video which'll help in understanding it. Thanks.
@@CodingSimplified in my opinion concurrenthashmap looks good when you want to have thread safety + decent performance. If in interview you are asked so then CHMP can solve some of your problems like concurrency, no race condition, efficient locking (bucket level), thread safety, better performance and scalable. Agree?
Greatly explained
Thanks.
Write back cache is protected using RAID levels usually now a days RAID 6 or 1and media is SSD. On the other hand cache through SSD along with RAID level directly on the IO module is most efficient but cotly process.
Hi, very nice presentation! Could you please upload it in English?
Great tutorial but what are you talking "you have multiple servers on a website". It's not correct. A website has multiple servers. And again " servers are hitting on the webserver" what does that mean? Do you mean "Requests are hitting on the webserver"?
Very clear explanation!
Thanks
Hi, Thanks for the video, I have a question.
While in the write around caching mechanism, it says it stores bypassing cache, directly into db. When it tries to load data, it makes cache miss then it gets data from db and then re-insult to cache.
My question here is, what if there was an existing cache, and make write-around method when writing that data. Then data will be affected in database, but it will not be affected in cache. What if we try to load that data again, then there will be that data in cache, and load old cache data.
Is this a disadvantage of write around cache? I thought that caching mechanisms only deal with latency for the load, so this case should not happen.
Please let me know if anything I'm missing from this concept. Thanks!
Hi, thanks for liking the video. Here our concept is about Cache Invalidation, which means we want to update cache with data. Now if we'll use old cache & showing old data, we're defeating our purpose. We need to show latest data, that's reason we can't use old cache here.
I hope it answers your question.
please do make the practical implementation of these concepts on Redis
ruclips.net/video/U3RkDLtS7uY/видео.html
@Coding Simplified. Where does the cache is stored in case of Distribute Cache
Good video, could u plz add some diagram it will improve video quality
Thanks for your suggestion. For this video, I can't add in between now. But, I'll take care in future. Thanks.
Hi, can you please suggest any book that i can find these concepts and your explaination is excellent ..thank you
Thanks. I'm not sure about book which contains these concepts.
@@CodingSimplified Thank you for the reply ..if you know any related books also please do suggest
@@yelletivarshith2398 grokking-the-system-design-interview
Hi, I belive that there is client(front end) & server(backend). Server means always backend. Say in case of web browser which is initiated from front end(client) & request is sent to backend (server). My doubt is - is there something like front end server also? When u say
web server, is it front end or backend? Can caching be done in front end/client side also without sending the request to server?
- when we say client, it means user, Now server can be at front end (UI) & at backend (API server)
- Caching can be done at front end as well on back end.
Let me know if you've any further questions.
Coding Simplified @ thanks for clarification. Other than user, can’t we say the UI(front end) is client ?
@@azadalishah2966 yeah, you can say. Just that, when you say, explain you're referring to front end.
Thanks
Thank you.
what do you mean when you say "web server has a single node"?
Means we are running only web server ( instance ) on node ( machine ). Which is available for all clients.
kaʃ
Hi , first of thank you very much for these videos.
can you please upload these ppts? that would be great :)
how much time data will reside in cache
It depends on size of cache. As far as cache size is not full, there is no time limit. It can stay for longer duration.
Data will be out from cache: If you flush cache or cache size limit is reached & least recently data is evicted
Great content, really informative. It's just amazing how you can say "applications" perfectly with a proper 'S' at the end, but you say "shtore" instead of "store", surely you can pronounce the sound 'S'....
Thanks for notifying. Atleast you're listening videos with attention. ;)
@@CodingSimplified Yes, especially this one. As I said, great content and really useful and concise! Keep up the good work.
Thanks