I interviewed a candidate recently and he mentioned to me about your channel. Thank you for the good content and teaching lot of people and helping them crack system design interviews,
20:28 overview of the design with example * 22:04 partition layer * 23:40 stream layer * 26:34 different partition strategies 27:34 stream layer * 28:06 store new file in append-only fashion * 29:00 seal file server that is full * 31:24 monitor space of all these file servers * 32:36 garbage collection performed on sealed file servers * 34:30 replication * 38:01 health check on the file servers * 40:32 block group 45:27 partition layer 48:56 performance improvement tips
At 28:06, you mentioned that spinning hard disk was a cheap feasible hardware solution for scalable storage service like S3 and SSD disk was expensive, I am interested to know if that is still true in 2022 since I know very little about detail architecture and marketing of SSD storage .
Just want to say that I really love watching these videos. Even if I'm not preparing for system design interviews, its fun to do these thought exercises to design a big system.
This channel covers a lot of ground and probably one the best channels. But...and a big but...It takes 2-3 times more time than needed. A lot of duplication, unrelated content which turns a 20 minute video into an hour video. For example, everything before first 20 minutes could have been finished in just 2-3 minutes. Please keep it short and precise. Appreciate all the hard work you put and the knowledge you are sharing. Keep going.
You are an amazing teacher bro. I am a frontend folk but I am still interested towards system design because of you. How the design are made the way you explain makes me very curious. Thanks for the big efforts. Cheers 👌
Thanks a lot for putting effort and providing design details of the distributed cloud storage. Although I had few questions:- 1. I see Cluster manager is SPOF, how do we handle if the CM is down ? 2. Why do we use DNS approach to update available Region routing ? Usually dns resolving is cached with few minutes or so, which will increase the downtime ? 3. How do we handle concurrent update(not append) for same file from different users ?
Really liked this comprehensive design session, great keep it up and all the very best. I really appreciate the the work you have done towards bringing such wonderful to us.
great content. Really appreciate it. I'm wondering, is it a good idea to start with a simple design and then scale up towards the final target design? I tried that at an interview and got the feedback that I didn't address many of the complexities until later in the discussion... Some other times I jumped into details upfront and got the feedback that I was focusing on details too much too soon....
Great Talk, I love this.. but to differentiate from others, Please anounce who is the audience and what is the depth level you would go in this video..for example, are you going to discuss algorithms used in design or overview of it.. if its scoped for an application developer or scoped for systems design developer...
This is the first time that I see how S3 works. Thank you so much!. I decided to focus my career on Distributed Systems as a Software Engineer, how do you get the base knowledge to design and implement a Distributed System?
The partition server + linked list of file servers idea seem like "Consistent Hashing on steroids"! Basically instead of a single server on a ring for a given hash range, it's an array of servers.
Hi Naren, thanks for your work. I have a question on uber/ food delivery design, from what i collected most of the applications rely on state machines to proceed to next step, could you please explain us how this Finite state machine is used in food delivery/uber designs
Really appreciate you putting up quality content. Very insightful . Couple of suggestions thougth - may be starting with high level user flow which you started talking at 21.00 will be useful. Also I am not sure both API server and Cluster Mgr two separate component talking to one DB is a good idea.
Great work, a small suggestions if it makes sense for you. Videos less than 20 minutes are appealing than longer videos. In case if it cannot be condensed then could be split in to parts. Awesome work on all your system design videos. Thanks
Not really, that can be left to the audience, I mean if you need break, you can pause, right? Also since this is a single entity, it's good to be a single video, honestly, I don't see any partitions here. Also psychologically imo if you recall the flow and feel something's hazy it's Less cognitive load to look for it in the flow compared to thinking between videos.
Awesome stuff as always! I have a couple of questions: 1. What impact will consistent hashing in realtime have on serving requests? 2. What will happen when a particular partition server goes down? Will it be replaced by a standby? How many standbys should you consider maintaining? 3. Is the Partition Map table a single point of failure? Or is it a within-cluster replicated data store? 4. Would there be any benefits to replicating a given file server within a cluster?
Great video! Only question I had is in the table you showed for the Stream manager, where it tracked the Start and stop offsets for the primary, it also had fields for the secondary and tertiary replicants, but it didn't separately track their offsets; that would need to be included as well, right? Thanks.
Great video keep going! I have only one remark, in minute 11 you said that replication must be in other region in case of a disaster, i think data must stay in the same region for some reasons (latency, RGPD ...) but in different Availability zones instead (this is the default option used by S3). Am i right ?
Ceph RADOS layer with remote replication can handle this much better. It also does not need metadata server for replication. Using CRUSH, proper availability can be guaranteed.
Time 48:10 Remapping of range from 0-100 to 0-50 and 50-100 is fine. But what happens to the files which are already written in the previous partition? How will the reads for UUIDs with hashes 0-50 map to the older partition?
In that case, the mapping is not updated till the new stream is already "warmed up", which means that the files with 0-50 hashes are already copied over to the new stream. Once this is done, there is a cut-over transaction in the partition manager DB which now starts routing the calls for 0-50 into the new stream. In the meanwhile, there might be files which got written to the old stream while this transaction was still happening. So that is handled by a catchup routine which ensures all files have been copied over. Imagine it to be a two stage commit : When the cut over begins, there is a soft commit which says : write all new files for 0-50 in new stream. At the same time, while reading, try reading from both new and old stream. Once all files are copied over and there's no stale writes left over in old stream, the commit is finalized. Now all reads and writes for 0-50 go to new stream, and some garbage collection happens for old stream to free up space. Hope this helps.
appreciate your share, but 1, I don't think different replications located in defferent Region, it costs to much to tranfser data between replications 2, i don't think the fail over switch is done by dns,
Given a set of processes running on a cluster of hosts , design a system that load balances the hosts through live migration of the process. The goal of the load balancer is to minimize or prevent recourse starvation, a situation in which processes are not allocated the amount of recourses they want to consume. In case where all hosts in the cluster are overloaded, we want to distribute recourses evenly across demanding process. Given an imbalanced cluster, we want to bring it to a banned state as soon as possible at the lowest cost. Can you do Load Balancer next:
How does Partition Server handle concurrent write requests if the system wants to honor append mode of writing to disk? One solution will be for a Single Stream - one can have multiple writers, each of which write to different file servers. However orchestrating such a model would be excruciatingly complex. Or Partition Servers can be logical entities with a 1-1 mapping to the stream id. Definitely that will lead to having many stream ids and some house keeping work for the Stream Manager. This will ensure the append mode of writing data and a better spread of file servers to stream ids. Let me know your thoughts Naren@Tech Dummies. Thanks for your videos.
Amazing Content! Really appreciate your efforts. One question - Do you need cluster manager in this architecture? Simple, failure, geo, weighted routing are supported by DNS mostly.
How do you do file and disk operations on the remote file server, from the partition server and the stream server (like copying, clearing up space from unused blocks, etc.)? Do you mount an NFS share on these servers and issue local shell commands on these remote shares?
The Cluster Manager is responsible for updating the DNS entries upon a cluster failure. What do you suggest doing for client-side caching of DNS queries?
what happens if a user wants to add more content to a file, (say file has 1-100 lines, and user wants to add 10 more lines to it) which is already in a sealed storage server? Will the file be copied to a new server? Or only the extending part in a different file server?
(Time 48:10) In case, when there is more load on the partition servers, the partition manager splits the range into two partition servers, how does this newly created partition server would talk to the older file server in the streaming layer (where the file was actually stored) Does anything change in streaming layer as well?
When partition manager assigns a new partition for a subrange say 1-50 out of 1-100, it also updates the partition map table entries. For example all the hash values say 14, 36, 42, 58, 89 were initially mapped to the partition server 2. Once the new partition server is added corresponding exiting stream servers in map table (14, 36 & 42) will be mapped to this new partition server. That way any further read request for those existing stream servers will be served by this new partition server.
how to store images or videos? what is the mechanism behind that? what have you explained it's for storing a file is okay but for photo/videos how it works?
I have a question. In your first simple design, you have a separate server to store metadata. On your second scaled storage system, where are the metadata stored? Is it all stored in the stream manager? Or is it stored on each individual partition server? Thanks!
Quick question, when the request of a file upload goes to the server, is it chunked on client side? if so where sync service will come into the picture?
does anyone know how cloud storage like Amazon S3 handle access control of each uploaded file ? for example , Amazon S3 exposes API endpoints for consumers to read and edit access control list of a file object , how does S3 do things ? really appreciate any reply or hints.
Lot of content, but language & presentation is quite poor. Because of that the flow is broken multiple times. This really doesn't help in an interview setting of 45 mins. The first major thing that an interviewer would want to see is the REST API signature of different functionalities offered , for example upload_file.
![ทางเดินชีวิต - ธีเดช ทองอภิชาติ x อ.ไข่ มาลีฮวนน่า [Official MV]](http://i.ytimg.com/vi/1f3wcG16dd4/mqdefault.jpg)
I interviewed a candidate recently and he mentioned to me about your channel. Thank you for the good content and teaching lot of people and helping them crack system design interviews,
20:28 overview of the design with example
* 22:04 partition layer
* 23:40 stream layer
* 26:34 different partition strategies
27:34 stream layer
* 28:06 store new file in append-only fashion
* 29:00 seal file server that is full
* 31:24 monitor space of all these file servers
* 32:36 garbage collection performed on sealed file servers
* 34:30 replication
* 38:01 health check on the file servers
* 40:32 block group
45:27 partition layer
48:56 performance improvement tips
At 28:06, you mentioned that spinning hard disk was a cheap feasible hardware solution for scalable storage service like S3 and SSD disk was expensive, I am interested to know if that is still true in 2022 since I know very little about detail architecture and marketing of SSD storage .
A friend of mine got into FB and APPLE. He found your channel (and couple of other SD channels) very helpful in his prep.
We can do this!
Thank you
Really your channel content not less than any other top online education platforms.
Appreciate your content 😊 Thankyou so much🙏
Just want to say that I really love watching these videos. Even if I'm not preparing for system design interviews, its fun to do these thought exercises to design a big system.
you got recognized by Kim Jong-un!
This channel covers a lot of ground and probably one the best channels. But...and a big but...It takes 2-3 times more time than needed. A lot of duplication, unrelated content which turns a 20 minute video into an hour video. For example, everything before first 20 minutes could have been finished in just 2-3 minutes. Please keep it short and precise. Appreciate all the hard work you put and the knowledge you are sharing. Keep going.
@Tech Dummies Narendra L: Could you please make videos on a centralized logging system and a distributed job scheduler?
Amount of work you put in making these 50 minute long videos is insane.
phenomenal work. we dont have to read books, they are for dummies :p
You are an amazing teacher bro. I am a frontend folk but I am still interested towards system design because of you. How the design are made the way you explain makes me very curious. Thanks for the big efforts. Cheers 👌
I appreciate your efforts. If possible, can you also share the references you go through for such design questions.
444r
He seems to read a lot of tech companies’ engineering blogs, based on his content.
really appreciate his effort , these engineering blogs in these tech companies are mostly very long articles
Thanks a lot for putting effort and providing design details of the distributed cloud storage. Although I had few questions:-
1. I see Cluster manager is SPOF, how do we handle if the CM is down ?
2. Why do we use DNS approach to update available Region routing ? Usually dns resolving is cached with few minutes or so, which will increase the downtime ?
3. How do we handle concurrent update(not append) for same file from different users ?
shandaar zabardast zindabaad!
Must say ,it would have taken much time for you to prepare this content , kudos !!!
Really liked this comprehensive design session, great keep it up and all the very best. I really appreciate the the work you have done towards bringing such wonderful to us.
Nice content....keep it up👍👍
Really appreciate the level of detailed information provided in this video. Thanks a lot for your hard work and creating such awesome content !! :D
Most valuable information ever on your channel.
Your channel is priceless brother, thank you.
great content. Really appreciate it. I'm wondering, is it a good idea to start with a simple design and then scale up towards the final target design? I tried that at an interview and got the feedback that I didn't address many of the complexities until later in the discussion... Some other times I jumped into details upfront and got the feedback that I was focusing on details too much too soon....
it's always a good idea to ask the interviewer.. what they are interested in..
Great Talk, I love this.. but to differentiate from others, Please anounce who is the audience and what is the depth level you would go in this video..for example, are you going to discuss algorithms used in design or overview of it.. if its scoped for an application developer or scoped for systems design developer...
Really Appreciate your video here. You explain it very clear.
This channel is gold!
This is the first time that I see how S3 works. Thank you so much!. I decided to focus my career on Distributed Systems as a Software Engineer, how do you get the base knowledge to design and implement a Distributed System?
Thank you Naren! Nice video. I could feel the effort which you have put to create such video.
Wow!! simply wow... Now I can cross question managers at Amazon during interviews
The partition server + linked list of file servers idea seem like "Consistent Hashing on steroids"!
Basically instead of a single server on a ring for a given hash range, it's an array of servers.
Excellent explanation. You didnt talk about the leader election and manager election in any of the layers but that's just some more detail.
Terrific presentation! Love your videos
Hi Naren,
thanks for your work. I have a question on uber/ food delivery design, from what i collected most of the applications rely on state machines to proceed to next step, could you please explain us how this Finite state machine is used in food delivery/uber designs
Really appreciate you putting up quality content. Very insightful . Couple of suggestions thougth - may be starting with high level user flow which you started talking at 21.00 will be useful. Also I am not sure both API server and Cluster Mgr two separate component talking to one DB is a good idea.
very nice presentation. Concise and good pronounciation. However, too much echo. Suggest to get a better recording system or infra with anti-echo.
great content
Appreciate the drastic improvement in delivery style.
this was great, can't wait to see more videos!
Thank you .. Great Explanation
Great work, a small suggestions if it makes sense for you. Videos less than 20 minutes are appealing than longer videos. In case if it cannot be condensed then could be split in to parts.
Awesome work on all your system design videos. Thanks
It's better to be at file.. otherwise it will break the flow.
Not really, that can be left to the audience, I mean if you need break, you can pause, right? Also since this is a single entity, it's good to be a single video, honestly, I don't see any partitions here. Also psychologically imo if you recall the flow and feel something's hazy it's Less cognitive load to look for it in the flow compared to thinking between videos.
Very well done!
thanks buddy, I do prefer the way you started with a simple architecture, and improve the system while increasing the traffic.
Appreciate your hard work behind it
Thank you for your time and efforts ,Its very helpful.
Awesome stuff as always! I have a couple of questions:
1. What impact will consistent hashing in realtime have on serving requests?
2. What will happen when a particular partition server goes down? Will it be replaced by a standby? How many standbys should you consider maintaining?
3. Is the Partition Map table a single point of failure? Or is it a within-cluster replicated data store?
4. Would there be any benefits to replicating a given file server within a cluster?
حء
مگر
جنگففےےےےےتےگءیءءءیثتسےڈےڈءءقرقر
قررقنرضنعضھڑضھھڑضھرگےرےڑےڑےڑثڑڑےثثثثڑحڑحڑءضءقءرءرقءڑقےڑضےڑتقتڑقءڑقحڑضیرءرقےرقفڑقےڑقیہقریءےن
نڑںڑچغدڑ
ڑنر
Nice
Hi Narendra, You awesome man! Keep posting ! Keep learning!!
Great video! Only question I had is in the table you showed for the Stream manager, where it tracked the Start and stop offsets for the primary, it also had fields for the secondary and tertiary replicants, but it didn't separately track their offsets; that would need to be included as well, right? Thanks.
Very nice videos including ur perspective on how to get jobs in germany, kerp going bro 👌🏻👌🏻
Great Stuff Narendra, I appreciate the effort you make in gaining all this knowledge from multiple sources and sharing with us. Thanks a lot.
awesome...very helpful
Great video keep going! I have only one remark, in minute 11 you said that replication must be in other region in case of a disaster, i think data must stay in the same region for some reasons (latency, RGPD ...) but in different Availability zones instead (this is the default option used by S3). Am i right ?
Yes, data is replicated in AZs of same region. There is an option to replicate data to another bucket in another region.
loved it mate!! thanks ❤️
good
Thanks for posting!!
Ceph RADOS layer with remote replication can handle this much better. It also does not need metadata server for replication. Using CRUSH, proper availability can be guaranteed.
Time 48:10 Remapping of range from 0-100 to 0-50 and 50-100 is fine. But what happens to the files which are already written in the previous partition? How will the reads for UUIDs with hashes 0-50 map to the older partition?
In that case, the mapping is not updated till the new stream is already "warmed up", which means that the files with 0-50 hashes are already copied over to the new stream. Once this is done, there is a cut-over transaction in the partition manager DB which now starts routing the calls for 0-50 into the new stream. In the meanwhile, there might be files which got written to the old stream while this transaction was still happening. So that is handled by a catchup routine which ensures all files have been copied over.
Imagine it to be a two stage commit : When the cut over begins, there is a soft commit which says : write all new files for 0-50 in new stream. At the same time, while reading, try reading from both new and old stream. Once all files are copied over and there's no stale writes left over in old stream, the commit is finalized. Now all reads and writes for 0-50 go to new stream, and some garbage collection happens for old stream to free up space.
Hope this helps.
Good contect however one doubt like if we are replicating from Europe to Asia isnt it Asynchronous replication?
this is very useful, thank you
appreciate your share, but
1, I don't think different replications located in defferent Region, it costs to much to tranfser data between replications
2, i don't think the fail over switch is done by dns,
Given a set of processes running on a cluster of hosts , design a system that load balances the hosts through live migration of the process. The goal of the load balancer is to minimize or prevent recourse starvation, a situation in which processes are not allocated the amount of recourses they want to consume. In case where all hosts in the cluster are overloaded, we want to distribute recourses evenly across demanding process. Given an imbalanced cluster, we want to bring it to a banned state as soon as possible at the lowest cost. Can you do Load Balancer next:
Great video but why can't ZooKeeper just do what Partition Manager does?
Mind blown!
How does Partition Server handle concurrent write requests if the system wants to honor append mode of writing to disk?
One solution will be for a Single Stream - one can have multiple writers, each of which write to different file servers. However orchestrating such a model would be excruciatingly complex.
Or Partition Servers can be logical entities with a 1-1 mapping to the stream id. Definitely that will lead to having many stream ids and some house keeping work for the Stream Manager. This will ensure the append mode of writing data and a better spread of file servers to stream ids.
Let me know your thoughts Naren@Tech Dummies.
Thanks for your videos.
"excruciatingly complex" sounds about right, there's a reason why only a handful of companies even try to get something like this working.
Amazing Content! Really appreciate your efforts.
One question - Do you need cluster manager in this architecture? Simple, failure, geo, weighted routing are supported by DNS mostly.
How do you do file and disk operations on the remote file server, from the partition server and the stream server (like copying, clearing up space from unused blocks, etc.)? Do you mount an NFS share on these servers and issue local shell commands on these remote shares?
The Cluster Manager is responsible for updating the DNS entries upon a cluster failure. What do you suggest doing for client-side caching of DNS queries?
S3 system use Object Storage instead of Block Storage as mentioned in 43:00 min, Correct me if I misunderstood.
Very Nice Video. One doubt, How Partition Server communicates to Stream Manager? As we don't have direct link over there..
what happens if a user wants to add more content to a file, (say file has 1-100 lines, and user wants to add 10 more lines to it) which is already in a sealed storage server? Will the file be copied to a new server? Or only the extending part in a different file server?
Something like RAFT or Frangimini or Spanner is always used for file servers
Why do we need partition layer? Why can't the API layer directly talk to Streaming layer since there is 1:1 of Partition to streaming layer anyway?
(Time 48:10) In case, when there is more load on the partition servers, the partition manager splits the range into two partition servers, how does this newly created partition server would talk to the older file server in the streaming layer (where the file was actually stored) Does anything change in streaming layer as well?
When partition manager assigns a new partition for a subrange say 1-50 out of 1-100, it also updates the partition map table entries. For example all the hash values say 14, 36, 42, 58, 89 were initially mapped to the partition server 2. Once the new partition server is added corresponding exiting stream servers in map table (14, 36 & 42) will be mapped to this new partition server. That way any further read request for those existing stream servers will be served by this new partition server.
@@amishsumit But a partition server is assigned to 1 stream only?
Solution 20:28
how to store images or videos? what is the mechanism behind that? what have you explained it's for storing a file is okay but for photo/videos how it works?
Good followup: How does PUT API work for large files?
Thanks, it would have been much better if you had related these concepts in terms of S3 keys and buckets
I have a question. In your first simple design, you have a separate server to store metadata. On your second scaled storage system, where are the metadata stored? Is it all stored in the stream manager? Or is it stored on each individual partition server? Thanks!
That will handled by cluster manager.
@@kinandchowdary6456 Stream manager dude
Quick question, when the request of a file upload goes to the server, is it chunked on client side? if so where sync service will come into the picture?
good question - shouldnt there be a chunk service - which splits the file into chunks?
does anyone know how cloud storage like Amazon S3 handle access control of each uploaded file ? for example , Amazon S3 exposes API endpoints for consumers to read and edit access control list of a file object , how does S3 do things ? really appreciate any reply or hints.
Do AWS regions each represent a continent? I thought "us-east-1" and "us-west-2" were both in the US.
Do you have any idea how to design a system load a 5G file to 5000 server?
how will the api insert data to the data store server?
Isn’t API server at 23 min nothing but a load balancer?
what technology do you use store the file? is it a database?
TCP
what happens if cluster manager goes down?
Hey , how can I deposit you the dollar 💵, this is too much work, I have an interview coming up and I’m watching all your videos , thank you
Thanks, Join the channel. You will find join button in the channel page!
I think noone today use spinning disks in production. At least in new projects. SSD are not so costly as they used to be.
do you know captain america
why not zip?
Is this a mid level answer?
Lot of content, but language & presentation is quite poor. Because of that the flow is broken multiple times. This really doesn't help in an interview setting of 45 mins. The first major thing that an interviewer would want to see is the REST API signature of different functionalities offered , for example upload_file.