What are Distributed CACHES and how do they manage DATA CONSISTENCY?

  Переглядів 965,419

Gaurav Sen

Gaurav Sen

День тому

Caching in distributed systems is an important aspect for designing scalable systems. We first discuss what is a cache and why we use it. We then talk about what are the key features of a cache in a distributed system.
The cache management policies of LRU and Sliding Window are mentioned here. For high performance, the cache eviction policy must be chosen carefully. To keep data consistent and memory footprint low, we must choose a write-through or write-back consistency policy.
Cache management is important because of its relation to cache hit ratios and performance. We talk about various scenarios in a distributed environment.
System Design Video Course:
interviewready.io
00:00 Who should watch this video?
00:18 What is a cache?
02:14 Why not store everything in a cache?
03:00 Cache Policies
04:49 Cache Evictions and Thrashing
05:52 Consistency Problems
06:32 Local Caches
07:49 Global Caches
08:56 Where should you place a cache?
09:35 Cache Write Policies
11:38 Hybrid Write Policy?
13:10 Thank you!
A complete course on how systems are designed. Along with video lectures, the course has architecture diagrams, capacity planning, API contracts, and evaluation tests.
System Design Playlist: • System Design for Begi...
Code: github.com/coding-parrot/Low-...
You can follow me on:
Facebook: / gkcs0
Quora: www.quora.com/profile/Gaurav-...
LinkedIn: / gaurav-sen-56b6a941
Twitter: / gkcs_
References:
Guava Cache - github.com/google/guava/wiki/...
LRU - www.mathcs.emory.edu/~cheung/C...
en.wikipedia.org/wiki/Cache_r...
Implementation of Sliding Window Cache policies (Caffeine) - github.com/ben-manes/caffeine
highscalability.com/blog/2016/...
docs.microsoft.com/en-us/prev...)
#SystemDesign #Caching #DistributedSystems

КОМЕНТАРІ: 525
@VrajaJivan
@VrajaJivan 5 років тому
Gaurav nice video. One comment. Writeback cache refers to writing to cache first and then the update gets propagated to db asynchronously from cache. What you're describing as writeback is actually write-through, since in write through, order of writing (to db or cache first) doesn't matter.
@gkcs
@gkcs 5 років тому
Ah, thanks for the clarification!
@KumarAbhishek123
@KumarAbhishek123 5 років тому
Yes, would be great if you can add a comment saying correction about the 'Write back cache'. Thanks for the great video!
@gururajsridhar7314
@gururajsridhar7314 5 років тому
I agree.. a comment in the video correcting this would be good update to this.
@mrityunjoynath7673
@mrityunjoynath7673 4 роки тому
So Gaurav was also wrong in saying "write-back" is a good policy for distributed systems?
@jyotipandey9218
@jyotipandey9218 4 роки тому
@Gaurav Yes that would be great. That part was confusing, had to read about that separately.
@waterislife9
@waterislife9 3 роки тому
Write-through: data is written in cache & DB; I/O completion is confirmed only when data is written in both places Write-around: data is written in DB only; I/O completion is confirmed when data is written in DB Write-back: data is written in cache first; I/O completion is confirmed when data is written in cache; data is written to DB asynchronously (background job) and does not block the request from being processed
@rajee120
@rajee120 Рік тому
Q
@GK-rl5du
@GK-rl5du 5 років тому
Other variants 1. There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors. 2. There are only two hard problems in distributed systems: 2. Exactly-once delivery 1. Guaranteed order of messages 2. Exactly-once delivery
@gkcs
@gkcs 5 років тому
Hahahaha!
@GK-rl5du
@GK-rl5du 5 років тому
@@gkcs A humble suggestion, I think you should have a sub-reddit for the channel, because these are such critical topics [not just for cracking interviews], I'm sure they'd definitely encourage healthy discussions. I think YT's comment system is not really ideal to have/track conversations with fellow channel members.
@RAJATTHEPAGAL
@RAJATTHEPAGAL 4 роки тому
This is an underrated comment .... 😂😂😂
@kumarakantirava429
@kumarakantirava429 4 роки тому
​@@gkcs Can you please give some hints on WHY "out of order Delivery" is a problem in distributed systems, if the application is running on TCP ..................PLease Kindly reply.
@kumarakantirava429
@kumarakantirava429 4 роки тому
@goutham Kolluru , Can you please give an hint on WHY "out of order Delivery" is a problem in distributed systems, if the application is running on TCP ..................PLease Kindly reply.
@mengyonglee7057
@mengyonglee7057 Рік тому
Notes: In Memory Caching - Save memory cost - For commonly accessed data - Avoid Re-computation - For frequent computation like finding average age - Reduce DB Load - Hit cache before querying DB Drawbacks of Cache - Hardware (SSD) much more expensive than DB - As we store more data on cache, search time increases (counter productive) Design - Database (Infinite information) vs Cache (Relevant information) Cache Policy - Least Recently Used (LRU) - Top entires are recent entries, remove least recently used entries in cache Issue with caches - Extra calls - When we couldn’t find entry in cache, we query from database. - Threshing - Input and output cache without ever using results - Consistency - When update DB, we must maintain consistency between cache and DB Where to place the cache - Close to server (in memory) - Benefit - Fast - Issue - Maintaining consistency between memory of different servers, especially for sensitive data such as password - Close to DB (global cache, i.e. Redis) - Benefit - Accurate, Able to scale independently Write-through vs Write-back - Write-through - Update cache, before updating DB - Not possible for multiple servers - Write-back - Update DB, before updating cache - Issue: Performance - When we update the DB, and we keep updating the cache based on that, much of the data in the cache will be fine and invalidating them will be expensive - Hybrid - Any update first write to cache - After a while, persist entries in bulk to database
@pushp3593
@pushp3593 4 місяці тому
nice, but write through and write back notes part is wrong, pls correct it. you can check other comments. thanks
@cheerladinnemouli2864
@cheerladinnemouli2864 2 місяці тому
Nice notes
@mannion1985
@mannion1985 4 роки тому
I can already hear the interviewer asking "with the hybrid solution: what happens when the cache node dies before it flushes to the concrete storage?" You said youd avoid using that strategy for sensitive writes but you'd still stand to lose upto the size of the buffer you defined on the cache in the e entire of failure. You'd have to factor that risk into your trade off. Great video, as always. Thank you!
@jsf17
@jsf17 3 роки тому
The world needs more people like you. Thank you!
@bhavyeshvyas2990
@bhavyeshvyas2990 5 років тому
Dude you are the reason for my system design interest Thanks and never stop making system design videos
@legozxx6655
@legozxx6655 5 років тому
Great explanation. You are making my revision so much easier. Thanks!!
@AnonyoX
@AnonyoX 4 роки тому
Great video. But I wanted to point out that, I think what you are referring to as 'write-back' is termed as 'write-around', as it comes "around" to the cache after writing to the database. Both 'write-around' and 'write-through' are "eager writes" and done synchronously. In contrast, "write-back" is a "lazy write" policy done asynchronously - data is written to the cache and updated to the database in a non-blocking manner. We may choose to be even lazier and play around with the timing however and batch the writes to save network round-trips. This reduces latency, at the cost of temporary inconsistency (or permanent if the cache server crashes - to avoid which we replicate the caches)
@kabooby0
@kabooby0 3 роки тому
Great content. Would love to hear more about how to solve cached data inconsistencies in distributed systems.
@jajasaria
@jajasaria 5 років тому
always watching your videos. topic straight to the point. keep uploading man. thanks always.
@SatyadeepRoat
@SatyadeepRoat 3 роки тому
I am actually using write back redis in our system but this video actually helped me to understand what's happening overall. GReat video
@rajeevkulkarni2888
@rajeevkulkarni2888 2 роки тому
Thank you so much for these videos!. Using this I was able to pass my system design interview.
@user-oy4kf5wr8l
@user-oy4kf5wr8l 4 роки тому
each of ur videos, i watched ay least twice lol, thank you!! WE ALL LOVE U! U R THE BEST!
@rishiraj9131
@rishiraj9131 2 роки тому
I also watch his videos mamy times. At least 4 times to be precise.
@semperfiArs
@semperfiArs 5 років тому
Extremely good video series bro. Just subscribed yesterday and loving it so far. Suggest you to start a interview series where you can answer a few important questions. Will be helpful.
@an_R_key
@an_R_key 4 роки тому
You articulate these concepts very well. Thanks for the upload.
@rahuljain5642
@rahuljain5642 2 роки тому
If someone explains any concept with confidence & clarity like you in the interview, he/she can rock it seriously. Heavily inspired by you & love your content of system design. Thanks for the effort @Gaurav Sen
@devinsills1281
@devinsills1281 2 роки тому
A few other reasons not to store completely everything in cache (and thereby ditching DBs altogether) are (1) durability since some caches are in-memory only; (2) range lookups, which would require searching the whole cache vs a DB which could at least leverage an index to help with a range query. Once a DB responds to a range query, of course that response could be cached.
@Sound_.-Safari
@Sound_.-Safari 3 роки тому
Cache doesn’t stop network calls but does stop slow costly database queries. This is still explained well and I’m being a little pedantic. Good video, great excitement and energy.
@mayankvora8329
@mayankvora8329 2 роки тому
I don't know how people can dislike your video Gaurav, you are a master at explaining the concepts.
@anjurawat9274
@anjurawat9274 4 роки тому
I watched this video 3 times because of confusion but ur pinned comment saved my mind thank you sir
@enfieldli9296
@enfieldli9296 2 роки тому
I just can't find a better content on YT than this, thanks man!
@vakul121
@vakul121 4 роки тому
It is a really great video.Finally found a detailed video.Thank you for sharing your knowledge!!
@zehrasubas9768
@zehrasubas9768 4 роки тому
Hi Guarav, I really like your videos thank you for sharing! I need to point out something about this video. Writing directly do DB and updating cache after, is called write around not write back. The last option you have provided, writing to cache and updating DB after a while if necessary, is called write back
@gkcs
@gkcs 4 роки тому
Thanks Zehra 😁
@harisridhar6698
@harisridhar6698 2 роки тому
Hi Gaurav - good video on distributed caching! This expands a bit more on what I learned in my computer architecture class - I didn't recall thrashing the cache too well, or what distinguished write-through vs. write-back. I think learning caching in the context of networks is more interesting, since it was initially introduced as a way to avoid hitting disk ( on a single machine ), but is also a way to reduce network calls invoked from server to databases.
@akash.vekariya
@akash.vekariya 3 роки тому
This man is literally insane in explanation 🔥
@kfqfguoqf
@kfqfguoqf 4 роки тому
Your System Design videos are very good and helpful, thanks!
@neeraj91mathur
@neeraj91mathur 3 роки тому
Nice video Gaurav, really like your way of explaining. Also, the fast forward when you write on board is great editing, keeps the viewer hooked.
@aswath_s
@aswath_s 3 роки тому
Awesome explanation gaurav. You're cool man. We want a lottt more from you. We admire your ability to explain topics with great simplicity.
@muhammadanas11
@muhammadanas11 3 роки тому
The way you explained concepts is AWSOME. Can you please create a video that decribes DOCKER and Containers in your style.
@Satu0King
@Satu0King 4 роки тому
Description for write back cache is incorrect. Write-back cache: Under this scheme, data is written to cache alone and completion is immediately confirmed to the client. The write to the permanent storage is done after specified intervals or under certain conditions. This results in low latency and high throughput for write-intensive applications, however, this speed comes with the risk of data loss in case of a crash or other adverse event because the only copy of the written data is in the cache.
@gkcs
@gkcs 4 роки тому
Thanks for pointing this out Satvik 😁👍
@justinmancherje6168
@justinmancherje6168 4 роки тому
I believe the description in the video given for write-back cache is actually a write-around cache (according to grokking system design)
@mostinho7
@mostinho7 3 роки тому
What if the cache itself is replicated? Will write-back still has risk of data loss
@arpansen964
@arpansen964 2 роки тому
Yes, as per my understanding, write-through cache : when data is written on the cache it is modified in the main memory, write back cache: when dirty data (data changed) is evicted from the cache , it is written on the main memory, so write back cache will be faster. The whole explanation around there two concepts given in this video seems fuzzy.
@prakharpanwaria
@prakharpanwaria 2 роки тому
Good video around basic caching concepts. I was hoping to learn more about Redis (given your video title)!
@JinkProject
@JinkProject 4 роки тому
this video was gold. studying for my facebook on-site and i need to understand a bit more how backend works. cheers @gaurav sen
@muraliboddu4007
@muraliboddu4007 2 роки тому
nice quick video to get an overview. thanks Gaurav. you are helping a lot of people.
@Not0rious7
@Not0rious7 3 роки тому
You continue to offer great content. thank you !
@jayantsogani8389
@jayantsogani8389 5 років тому
Thanks Gaurav, your lecture helped me to crack MS. Keep posting video's
@gkcs
@gkcs 5 років тому
Congrats!
@shubham.1172
@shubham.1172 4 роки тому
Are you in the Hyd campus?
@TheHalude
@TheHalude 4 роки тому
Thanks this was a good video for a high level overview of cache, easy to follow,
@happilysmpl
@happilysmpl 2 роки тому
Excellent! Great video with tremendous info and design considerations
@OwenValentine
@OwenValentine 4 роки тому
Gaurav, what you initially described as write-back at around 10:30 I have seen described as write-around. Write-back is where you write to the cache and get confirmation that the update was made, then the system copies from the cache to the database (or whatever authoritative data store you have) later... be it milliseconds or minutes later. Write through is reliable for things that have to be ACID but it is slower than write back. You later describe what I have always heard as write-back at around 12 and a half minutes
@gkcs
@gkcs 4 роки тому
Yes, I messed up with the names. Thanks for pointing it out 😁
@grijeshmnit
@grijeshmnit 4 роки тому
Your explanations are improved a lot now... correct sequence of information was missing in your earlier vdos... May you can improve your flow chart, fig further for less confusing...
@NohandleReqd
@NohandleReqd 2 роки тому
Teaching and learning are processes. Gaurav makes it fun to learn about stuff, then let it be systems or the egg dropping problem. I might just take the InterviewReady course to participate in the interactive sessions. Take a bow!
@manasbudam7192
@manasbudam7192 4 роки тому
What you explained as write-back cache is actually a write-around cache. In write-back cache...you update only the cache during the write call and update the db later (either while eviction or periodically in the background).
@timhomstad
@timhomstad 2 роки тому
Do you implement caching on most systems? It will add complexity, how can you determine if it is worth the additional effort to develop. Love the videos by the way. These are a great learning tool, you do a great job.
@renon3359
@renon3359 5 років тому
Keep making these videos brother, great job as always. :)
@andreigatej6704
@andreigatej6704 5 років тому
Very well explained! Thank you
@codingart7736
@codingart7736 5 років тому
Loved your sharing Thanks a lot
@CloudXpat
@CloudXpat 3 роки тому
Great explanation for caching. I believe you'll go far.
@silentknight2851
@silentknight2851 4 роки тому
hey Gaurav, for holidays I'll watch your videos day in and day out... So please teach new topics asap. I love to listen you
@sandeepk9640
@sandeepk9640 3 роки тому
Nicely packed lot of information for glimpse.. Great work
@asankaherath1744
@asankaherath1744 3 місяці тому
Thank you so much..! your videos are really valuable. Really appreciate your effort, sir.!!
@psrajput09
@psrajput09 5 років тому
Superb, now I started using my free time to learn something ! Thanks!!!
@shreyasns1
@shreyasns1 2 роки тому
Thank you for the video. You could have gone a little deeper about how the cache is implemented? What’s the underlying data structure of the cache?
@pat2715
@pat2715 3 місяці тому
amazing clarity, intuitive explanations
@djanupamdas
@djanupamdas 5 років тому
I think simply telling THANK YOU will be very less for this help !!! Superb video.
@gkcs
@gkcs 5 років тому
Glad to help :)
@jagatsastry
@jagatsastry 4 роки тому
I mean you can always do more by becoming a channel member 😄
@oscarjesusresendiz100
@oscarjesusresendiz100 4 роки тому
Great explanation Dude! You killed it!
@RpraneelK
@RpraneelK 2 роки тому
Very informative and concepts explained clearly. Thanks
@nishantmahajan55
@nishantmahajan55 4 роки тому
Very helpful and to the point. Thanks.
@souradiptachoudhuri4724
@souradiptachoudhuri4724 5 років тому
This video is just awesome. Thank you
@1970mcgraw
@1970mcgraw 3 роки тому
Excellent info and presentation - thanks!
@ashwinasokan
@ashwinasokan Рік тому
Bhai. u r a life saver! Brilliant tutoring. Thank you!
@akashnag3879
@akashnag3879 5 років тому
Loved it.. Thank you for such amazing video.. keep coming up with more.
@ravimulchandani2916
@ravimulchandani2916 Рік тому
Nice Explanation Gaurav. This video covers basics of caching. In one of the interviews, I was asked to design the Caching System for stream of objects having validity. Is it possible for you to make some video on this system design topic?
@jatinchugh373
@jatinchugh373 5 років тому
dude your content is amazing
@rsragsh55
@rsragsh55 4 роки тому
Hi Gaurav, Your videos are awesome and of great help. Would really appreciate if you could make a video regarding ''how to get aws certification''.
@jask00
@jask00 5 років тому
Great job. Really well explained
@i2chang
@i2chang 4 роки тому
Thank you, this video is very good!
@michaelscheppert3664
@michaelscheppert3664 2 роки тому
thanks for this quick tutorial :) your English is really good
@kevinz1991
@kevinz1991 2 роки тому
learned a ton in this video thanks so much
@rahulchawla6696
@rahulchawla6696 Рік тому
wonderfully explained. thanks
@billyean
@billyean Рік тому
Explained like my interviewed candidate today.
@zainsyed9811
@zainsyed9811 4 роки тому
Awesome overview thanks. One other possible issue with write-through - it's possible to make the update to the cache then the DB update itself fails. Now your cache and db will be inconsistent.
@gkcs
@gkcs 4 роки тому
True 😁
@ivandrofly
@ivandrofly 4 роки тому
My boy look very energized... keep it up!
@gkcs
@gkcs 4 роки тому
😁
@rishiraj1616
@rishiraj1616 5 років тому
This is my video on your channel and I must say that you explain very well! You seem professional, knowledgable and researched your topic well!
@PalashPathak19
@PalashPathak19 5 років тому
Hi Gaurav, it is refreshing to see your System Design videos. I have a small doubt. You initially suggested that In-memory caching is not such a good idea & that we should rather use Distributed Global caching. So why did you compare write-through & write-back focusing on In-memory caching? Which one would fare better when used with Distributed Global caching? (as consistency will not be an issue in that case) Thanks in advance.
@anmolbisht8562
@anmolbisht8562 4 місяці тому
i also have a same doubt
@GustavoRodrigues-le3zw
@GustavoRodrigues-le3zw 2 роки тому
Amazing Explanation!! Thanks!!
@kartikpandey3631
@kartikpandey3631 4 роки тому
Hi Gaurav, great video and nice presentation skills (y). Just wanted to know if we can use write-through with global cache will it be a better approach as there will be consistency as well as high performance of write-through? and can it be used for critical data ?
@kumarp1976
@kumarp1976 3 роки тому
Good content. However, the Hybrid approach is based only on write through. There should be a Hybrid approach on write back too. The system (post db entry) should also not just invalidate, but update the cache with new data. That way, both persistent and cache storage has new data. No cache miss for next read. What do you think @gaurav?
@CodeSbyAniz
@CodeSbyAniz 3 роки тому
You have explained it very nicely. Thanks.
@sirunworld
@sirunworld 3 роки тому
Great going, Gaurav. You have a great future!
@ananava254
@ananava254 3 роки тому
Thank you Gaurav, it was a really good explanation
@chriszeng5406
@chriszeng5406 4 роки тому
Good video. Thank you. From Canada.
@meletisflevarakis40
@meletisflevarakis40 4 роки тому
Your explanation is awesome. Keep it up!
@gkcs
@gkcs 4 роки тому
Thanks!
@raghavabharati
@raghavabharati 4 роки тому
Pls refer to the caching topic page in Educative(That you've recommended). Is the explanation in your video and that page aligned?
@sharifulhaque6809
@sharifulhaque6809 3 роки тому
Very easy understanding Gaurav. Thanks a lot !!!
@sakshichawla3946
@sakshichawla3946 2 роки тому
Very well explained !!
@chenwang7194
@chenwang7194 3 роки тому
Nice video, thanks! For the hybrid mode, when S1 persists to DB in bulk, the S2 is still having the old data, right? How do we update S2?
@ShaliniNegi24
@ShaliniNegi24 4 роки тому
Nice Explanation! Thanks :)
@hareendranep8422
@hareendranep8422 4 роки тому
Very nice presentation . Simple, powerful and fast presentation. Keep up the style
@gkcs
@gkcs 4 роки тому
Thank you!
@siris3957
@siris3957 4 роки тому
You explain so well! :) Thank you
@gkcs
@gkcs 4 роки тому
Thanks!
@mana5473
@mana5473 2 роки тому
Great video, thank you!
@shoaibzafar5663
@shoaibzafar5663 Рік тому
This everything what I needed. I am really looking forward to learn that how can create an online game hosting server . I researched a lot on how do it and I didn't get it what is exactly happening. Your CDN video was really good 👍. Now I have understood how exactly CDN works and why it uses distributed caching 👍💯
@gkcs
@gkcs Рік тому
Thank you 😁
@AbhideepChakravarty
@AbhideepChakravarty 3 роки тому
The draw back of write through you explained is equally applicable in Write Back i.e. I null the value in S1 still the value is not null in S2. Major thing is - Redis is not distributed cache. Even their own definition does not include the word "Distributed" - Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes with radius queries and streams. Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability via Redis Sentinel and automatic partitioning with Redis Cluster.
@VikramKumar-qo3rg
@VikramKumar-qo3rg 3 роки тому
Fun part. I was going through 'Grokking The System Design Interview' course, found the term 'Redis', started searching for more on it on youtube, landed here, finished the video and Gaurav is now asking me to go back to the course. Was going to anyway! :)
@gkcs
@gkcs 3 роки тому
Hahaha!
@thompson7440
@thompson7440 5 років тому
Thanks for the great video! And I actually have a question about write through cache and why is it bad for handling financial data? Because it needs to write to both cache and memory and that would increase the I/O cost or there might be some inconsistency when another processor access the data from memory between the gap of writing into cache and writing into memory?
@gkcs
@gkcs 5 років тому
Thanks! It's the latter.
@kiranpanda8161
@kiranpanda8161 5 років тому
Hi Gaurav. Got little confused. I feel, if something is global e.g. Reddis it's called a shared cache. Whereas, storing/having cache implemented on server (specific to a node) is called distributed cache, which can be updated (or kept in sync) using multicast protocol. Correct me, if I am wrong. As always, your contribution to the community is much appreciated.
@gkcs
@gkcs 5 років тому
I'll look this up. It's possible I mistook the terminology 🙂
@bala9893
@bala9893 5 років тому
You made what i want😍
@liba01
@liba01 3 роки тому
You are great, dude!
@mkgcodes
@mkgcodes 5 років тому
This one is very helpful for me. Many thanks Gaurav.
@gkcs
@gkcs 5 років тому
Cheers!
@muthupandi4371
@muthupandi4371 4 роки тому
Excellent explanation
@fakhruddintahery1561
@fakhruddintahery1561 Рік тому
Great explanation
System Design Interview - Distributed Cache
34:34
System Design Interview
Переглядів 340 тис.
What is an API and how do you design it? 🗒️✅
15:26
Gaurav Sen
Переглядів 703 тис.
Teenagers Show Kindness by Repairing Grandmother's Old Fence #shorts
00:37
Fabiosa Best Lifehacks
Переглядів 31 млн
skibidi toilet 73 (part 2)
04:15
DaFuq!?Boom!
Переглядів 30 млн
Data Consistency and Tradeoffs in Distributed Systems
25:42
Gaurav Sen
Переглядів 176 тис.
Redis Crash Course - the What, Why and How to use Redis as your primary database
23:37
WHATSAPP System Design: Chat Messaging Systems for Interviews
25:15
Gaurav Sen
Переглядів 1,8 млн
How I Mastered System Design Interviews
10:22
Ashish Pratap Singh
Переглядів 47 тис.
Cache Systems Every Developer Should Know
5:48
ByteByteGo
Переглядів 426 тис.
20 System Design Concepts Explained in 10 Minutes
11:41
NeetCode
Переглядів 830 тис.
Should You Still Learn To Code In 2024?
15:12
Tina Huang
Переглядів 63 тис.
How to Crack Any System Design Interview
8:19
ByteByteGo
Переглядів 272 тис.
Best OS for programming? Mac vs Windows vs Linux debate settled
8:41