This was the first video I'd seen from this channel. This is some next-level system design content. Way more in-depth than other videos I've seen. Unfortunately, it doesn't look like there have been any recent uploads, which is really too bad.
this is the best video for systems design I've ever watched. I listened to it at 50% speed to write down every word whereas I usually watch YT vids at 1.5x -- each sentence was invaluable.
This is absolutely the best content on RUclips on the system design topic! No "scratching the surface" bullshit, but rather very in-depth and concrete explanation on how to navigate successfully through the system design interviews. Thank you Mikhail for your great efforts! Большое спасибо, Михаил! One thing bothers me though, there haven't been any recent updates on the channel. I'm pretty sure, all the people here will appreciate and support if Mikhail decides to continue his endeavours and uploads new videos! Anyway, thanks a lot!
Normally I play videos in 1.5x or 2x. Your videos have so much information that I am afraid of losing some fundamentals if I play in 2x. Outstanding quality. Please keep making such videos.
Appreciate your efforts on aggregating and delivering such quality content in such a lucid manner. I don't think there is better content than this anywhere on youtube especially for system design topics. Wow ! (Y)
I almost never comment on RUclips but this undoubtedly deserves an exception. Thank you for the superb quality content you’ve put together. I wouldn’t be surprised if this series becomes the de facto video resource for systems design and architecture interviews. Hope you keep uploading!
5:10 load balancer availability/single point of failure, can assign multiple A DNS records for our domain (multiple IPS ) when we want multiple load balancers 8:00 usd cases for frontend service 9:15 request deduplocation to achieve exactly once or at most once semantics (the ack response could be lost when sending back to user, so user will retry and we don’t want to process duplicate requests that we already housed) 12:00 reusable components for other system designs
can't thank you enough for this video. All of these components are building blocks and the interviewer can dig deep as to how the requests are handled from client to server. Awesome video
Mikhail is the best. His system design videos are systematic and top notch with respect to quality and crispness. Presenting how to finish a complete design in 35 to 40 mins Wow, this is a great feat and only way for us. Prior to watching these videos my ideas and presentation is messy and dis-organized, but these videos gave me the basic sense what is expected in System Design and how to approach it. I take down the notes while watching the videos and try to apply these principles to other interview questions. This is greatly helping with my preparation. Can't thank you enough Mikhail, you are one of my best teachers.
I don't think any other youtube video on System Design goes this deep into explaination. Thanks for your efforts in bringing these videos to all of us.
Thank you for summarizing precisely about what can be covered in a 40 minute time limit. Knowledge is one part which is built over learning and experience. Your video really helps to focus on structuring and expressing the knowledge in a coherent manner. Thank you.
13:17 Strictly speaking, using a database as a backend message store is a valid option (because database = storage engine + high level type system). The problem is that FIFO message ordering semantics, that is usually expected from queues, is not easily achievable on the top of off-the-shelf databases. Because the latter are usually designed for a different query/update patterns than it's common for queues. But some databases can handle this custom case perfectly, and some queues (Kafka) are even positioning themselves as a databases.
These videos are best resource among all I have gone through. I am surprised, why this channel is not posting any more videos. Good Work and thank you !
I bought your course. Arguably the best investment I made for system design courses so far. Thanks for putting together contents and explaining them so lucidly. I look forward to other two modules.
This is the best distributed message queue system design I have seen so far. Many good concepts introduced and summarized , I feel it very helpful by using it as a guideline and read the other documents for more details such as the AWS SQS document. Looking forward to more content in the future.
It is full of quality content, It took me around 2-3 hours to completely watch along with preparing notes for this video. And 9 pages of notes it is, initially I thought it would be in 3-4 pages only. It's full of rich content, that I had to note everything down. Thank you. I am looking for a better way to prepare for System Design questions. With this speed, I am not sure how much time It will take for me.
Hi Mukesh. You are right, preparation for a system design interview is a lengthy process. And it greatly depends on the level you plan to apply and your background. Just take one step at a time. First, try to learn about concepts without going too deep into each one of them. Otherwise, you will find yourself traversing a very deep graph of various interconnected concepts. Second, go deeper with every next iteration, if time allows. Third, use your daily work as a constant source of knowledge. Ask yourself how things in your project/application work. And do not stop asking yourself until you get a pretty solid understanding of a particular feature. It is a big and a very good question you've raised. I should, probably, create a video on how to prepare, depending on how much time one's have.
I have been following some system design channels on youtube and this one is by far the best. Well structured, it discusses tradeoffs, solutions are clear.... In one word, AWESOME! Thank you very much.
17:08 to clarify option 2, queues are basically each a cluster in this case(each cluster contains a set of queues). Instances are the replications. Interestingly replication for inmemory hosts/instances are handled similarly to nosql nodes
I have seen a bunch of youtubers for system design interview...this one is one of the better ones...good way of using graphics while talking instead of mundane approach of heavy talking and using a whiteboard....Great job buddy...I am gonna explore all your video now
This is pure GEM!.. Amazing crystal clear explanation on Distributed computing concepts. Best tutorial till date on whole of youtube for system design prep material... Great work
Just awesome ! Your approach to problem solving is very generic. Really liked it and keep posting such fantastic system design interview questions. This is the best material i have seen till date on the topic. Thanks a lot.
Summary(notes): 1. Problem statement: Producer sends data and exactly one of the consumers gets the data 2. Resolving ambiguity in the problem statement by asking questions such as scale, priority, and so on... 3. Just focus on the core set of requirements - sendMessage(messageBody), receiveMessage() 4. SLA numbers for the non-functional requirements 5. Components: LB, Control Plane(Metadata-Service), Data Plane-1(Frontend), Data Plane-2(Back-end) 6. FE: Required Cross cutting concerns such as billing, throttling, the most important - routing to Backend since the Backend is stateful and so on. 7. Metadata Service: Caching Layer for routing information and metadata ( high consistency required in case of very few writes, R/W Ratio) 8. Backend Service: API Handling Layer, Storage and so on. Since Backend has to be HA and fault tolerant as it requires a consensus service like ZooKeeper or In-Cluster and Out-Cluster management strategy. ---- Extend the above design of queue creation with queue deletion, message deletion, message replication, delivery semantics( exactly once delivery not supported because it requires 2PC) and Pull vs Push messages, security and monitoring. --- Scalability Bottlenecks, use-case exntensability and use-case supported/limitations?
Your videos are Superb ! Most useful videos on System design. Please start making more videos like this ! More on each component details which helps in System design :) !
I'm surprised I've not found this sooner. One of the best resources for System Design. Sadly, I think Mikhail has stopped making the content. I hope you read this and do make more awesome content! Subscribing in case you do!
Thank you for all the hard work and such a great explanation of complicated topics. This is way superior to other paid content. I would love to see video on API design that covers how and what. For example, question that say design an API to upload photos from iOS, how do you go about it? What are the good characteristics of an API? What are key components you need to think about while designing an API and so on.
Thanks allot @Mikhail. Your videos are so fun and easy to watch. I feel it's one of the best specifically for system design and you sound like some Russian Pro coder to top it;) I request you to make a video about all the possible components (load balancers, CDN, etc) in a system design interview that will ever be used, because you keep using few different components for different problems. If we get to know all the components, then we too can arrive at a better solution. Thanks for the great content and keep creating new videos! 👍
Thank you for the kind words, Chirag! I have been thinking about the same for a while. And there are ideas how to address this. Just need to find more spare time to realize all these ideas ((
This video is great quality. I think sequential writes should have been suggested in the video. This seems to me the best way to achieve high throughput.
Hi Reyaz, you can use inbuilt feature for subtitles provided by RUclips player. Click on the icon labelled with cc while playing the video. hope it helps until Mikhail provides the subtitles. Thanks
Really comprehensive coverage of the topic! Although, would've loved to see more discussion on Asynchronous out-cluster replication. It's tricky to design, eg. what happens when you receive a get request while the data hasn't fully replicated across hosts in a cluster? can we hit all hosts in a cluster? what happens if we receive a get request when the message deletion replication is in progress etc.
Thank you so much for your videos. I have watched all videos in your channel. Waiting for your distributed database video. Hopefully you are still running this channel
Great content! Thank you for making this. One thing that seems not clear (at least to me) ~min15-min17 you show the flow of the message from FE to backend node and to receiver. It is unclear how do you separate persisted information between MS (database) and in-cluster manager (ZooKeeper). Both seems to store mapping between Queue name and Leader Host. Do you really need to store this information in two places? How are they synchronized? Why would you need to keep this info in the MS in the first place? Isn't ZooKeeper enough for queue-to-node mapping?
Both options are fine: 1. When we store mapping in the Metadata service. Zookeeper is used for leader election and leader monitoring. And if leader changes, this information is propagated to the Metadata service. 2. When we store mapping in Zookeeper. Zookeeper is highly optimized for reads. Anyway, this information is stored in one place. So that we avoid any synchronization between configuration storages and have a single source of truth.
Thanks a lot for your videos! Very helpful! I wonder if it's possible for you to have a mock interview video (e.g. you're on the interviewee side), covering things like what tools/apps would you use for real-world SDIs for better productivity, etc.
15:20 why was leader-follower option A? Why not use a loadbalancer? Why not use sharding to pick a queue, or have all machines be equal nodes, and pick a random one? Summary of option A and B: A uses leader to cleanup and replication B instances are equal, but still need something to handling of each instance
Regarding how the front end service finds the leader backend nodes, you mention that this discovery would be done via metadata service. But in the in-cluster method, we actually have that information in the coordinator service (zookeeper). In this case, would the metadata service just be a thin wrapper for the coordinator service (in case of backend node discovery)? Thank you so much for sharing these videos Mikhail. (Also, I love that you mention several times that the interviewer is there to help us, I find it delightful to have that perspective, and definitely helps during the interview)
Hi Suharto, Thank you very much for the feedback! Regarding your question, we can use either Metadata service or Zookeeper itself for storing and retrieving information about leaders. Please take a look at my answer here: ruclips.net/video/iJLL-KPqBpM/видео.html&lc=UgxAE6YfMUj95phbLid4AaABAg.90QChp-3ylO93AokcEr3Bu
A few questions - at 10:12 you say that "read when mesg arrives, write only when queue created". why? wouldn't you write every mesg arriving to the cache? - metadata service is it responsible for persisting data to db other than being used as cache? if so why is backend service also doing the same? - when you say distributed queue, you mean queue for communicating between a single producer-single consumer resides on several machine or between several "single produce-consumer" connections on several machines? if former, wouldn't only one machine be sufficient?
Hi Jm Ka, 1. Metadata service is used for storing meta information such as queues to backend service host mapping so when we create a new queue then only we need to add that info to Metadata Service persistent storage and cache as well. 2. Backend Service stores the actaul message and based on the requirements we may cache for frequeuent accessed queue to Metadata Service.
Hi Jm Ka, Hopefully Mitesh's answer helped to clarify what is stored where. Metadata service for metadata only and Backend service for messages. As for your last question, can you please clarify what yo mean by "several single produce-consumer connections"? Each message lives on several machines. To achieve high availability. Simply speaking, we want to make sure that messages are not lost if a single machine crashes. Every time we store a published message, we replicate it. So, we always have several copies of the same data.
@@SystemDesignInterview Hi, Mitesh's post doesn't answer anything, it's simply reiterates stuff he heard you say. 1) was how at 10:12 for metadata service you say "read when mesg arrives, write only when queue created". Is metadata service (or cache) storing the whole queue including messages? Or is it storing only which queues go to which consumers? Either way, when a message arrives, then too it'd need to be cached in metadata service, so there has to be a write. In that case, saying ""read when mesg arrives, write only when queue created" would be wrong 2) Is metadata service only a cache or can front-end service persist messages without going through metadata service? backend service persists messages, but it looks like in your description metadata service is doing the same too? 3) by the term "distributed queue", one could mean several things. A) you can have a distributed queue that's conceptually a single queue for only 1 producer that's generating messages for 10 consumers, but the queue is replicated and sharded on several machines for availability concerns. B) you could have a distributed queue that's multiple queues for 5 different producers, each one catering to 10 consumers (total of 50 consumers). this queue can also be called distributed. C) a distributed queue that's multiple queues for 5 different producers, each one catering to only 1 consumer (total of 5 consumers). By "several single produce-consumer connections" I meant case (C). Which one of A or B or C you meant by "distributed queue"?
Hi Jm ka, 1. We write to Metadata service only when we create/update queue metadata. We do not store messages in Metadata service. When message arrives, we make a call to Metadata service to get details about the queue. E.g. we may retrieve message size limit value and check if the just arrived message exceeds the max size or not. Messages are only stored on back-end service machines. Please let me know what part of the video confused you and made you thinking we store messages in Metadata store. 2. When message arrives, front-end service needs to pick a back-end machine for storing the message. Same is true for retrieving a message, front-end needs to forward receive message request to a machine that stores messages for the requested queue. So, front-end needs to get this information from somewhere. From some persistent storage. Calling database directly is not great in this case, as there may be too many calls. This may be both slow and expensive. Metadata service helps to avoid direct calls to the database, by storing queue metadata information in memory. 3. Distributed simply means messages for the same queue are replicated and stored across several machines. There may be multiple producers and multiple consumers. Only one consumer gets the message. Let me know if you have other questions.
Great content! I have some confusion regarding the queue identification. 1. In the API definition, we are only sending the message, so when the first-ever message comes, how is that message getting mapped to a queue number? For example in the slides it says a sendMessage(msg) comes for queue id =1, how does the sender know about the queue id? Similarly, when the receiveMessage() API is called, how does the receiver know which queue to get the message from, secondly there are several messages in the queue, so how do we know which message it wants to receive, and how are we deciding? Let's say., when the first message comes around, the backend stores the data and takes care of replication, then writes the mapping in the DB. But how is this information being propagated to the receiver, that wants the message, how do they get to know about the queue id? 2. In the table shown for in-cluster management, for qid 1, the leader is A and followers are C, B. But if the queue is distributed over nodes, then how are we just having one leader node as A? Doesn't that mean we are storing the entire queue 1 in A, and the copies in the followers?
1a. Message should contain QueueId. 1b. API should be queue.ReceiveMessage() ; Queue object knows about queue_id and sends in either every poll request or is tied to tcp/grpc/websocket connection. 1c. Messages are received from queue in kind of FIFO order. So, client sends last Message id or Sequence Number and server sends SequenceNumber+1 th message. 1d. Client knows queue name and that should be able to give them queue id. It can be either hash of "queue_name" Or they ping Frontend service to get QueueId for a QueueName. 2. A distributed queue does not mean partial data on different nodes. It means full copy of data on all nodes. One of the node can only currently write -- this node is called Primary node. This is done so that even if one machine goes down for ever, full copy of data is available in other machines. This gives high availability/durability in case of failures.
10:31, why does the architecture show a single DB for A-Z records, doesn't it defeat the purpose of having shards across MS. I would think that each MS manages the shard it is responsible for ?
Thanks for the great content. Can you please talk about which choice of architecture (1, 2 or 3) you would make for the Metadata Service? And why? And please explain your comment that the datastore for MS does not need to be strongly consistent?
Great video, very in depth I have a question concerning option b for the backend service architecture (Small cluster of independent hosts) The frontend calls the meta service to find out the instance responsible for the queue yet calls a random instance. If it’s going to call a random instance why call the meta service?
In the backend storage design, Option B, one node in the pool of the backend hosts is responsible for distributing messages to other hosts in the pool. The downside with this approach as I see is that the client(sender Front end) has little idea about how many hosts the message is actually distributed to. What happens if the receive call selects a host which does not have the message? Wouldnt it make more sense to have a quorum based read and write approach at the front end service layer. Where it sends a send request to x hosts and wait for x acknowledgments and receive request is sent to y hosts and wait for y responses. As long as x+y > total hosts in the pool a consistent read is guaranteed. Of course this is assuming consistent reads are needed and strict ordering is needed which adds to latency. Also a little unclear on the role of metadata service here? Specifically what information does it store if there is another out cluster manager for hosting information about queue to cluster mapping.
This frontend service looks more like a backend service to me and @15:55 ,does FrontEnd recieve a message from queue, and then communicates to Backend / Message Service (blue)?
These are really nice videos with quality content. Suggest you to slow down a bit. Just a doubt: in 5:58 you talk about using VIP partitioning and spread it to multiple data-centers. With this should the Meta-data store and backend-store be replicated in each of the data centers. Because due to dns load balancing the request can go to any load-balance and the data-centers that the producer api hits( sendMessage() ) and the consumer api hits ( recieveMessage() ) can be different. Can you pls shed some light on this. Thanks!
Awesome video. The only thing that was a bit confusing for me was the part about in-cluster manager (zookeeper) - It wasn't clear if zookeeper is in fact the Metadata service or an additional component (along side MS).
Hi Michael. Thanks a lot for the feedback! Here I left my view on why separation for out-cluster manager approach (multiple clusters) makes sense: ruclips.net/video/iJLL-KPqBpM/видео.html&lc=UgwD2gh8ozvKz1wMqId4AaABAg.99gLjSiA1G79BLjjputJT6 For the in-cluster manager approach, we can indeed use a single component. And the way Kafka uses Zookeeper proves this. As Zookeeper is "especially fast in "read-dominant" workloads." (from the official Zookeeper site). Although, I still prefer to separate these components for the in-cluster approach as well. There are many arguments in favor of one approach or another.
Thank you for great quality content. Excellent explanation, I can't miss single word. Why the series is stopped? Any other resources would you recommend?
Thanks for sharing the design. May I ask a question? As you mentioned at 1:22 of the video, in case of queue, the message is received by one and only one consumer. Does it mean, we should create a queue for every consumer?
Great video, thanks for doing these. Can you please explain why we need a FE component? Initially I thought it was to design a distributed message queue, the ones used by the backend services, like the one that you had drawn in your other video: System Design Interview: Step by Step Guide. Or is this a question about how to design a chat appication? And then my last question is, can we combine VIP with load balancer into one component, the API gateway? Thanks!
Really great content. I have one doubt. In the out cluster management option, let's say we split each queue into multiple partition across multiple clusters, and each partition is being handled by separate clusters with replication of data in all the nodes inside the cluster. What if an entire cluster goes down? How will we ensure durability of the message belongs to the partitions managed by that cluster.. Please help me to resolve the doubt.
Can you please talk why you would use log files to store the data rather than the database? I have an idea but I would like to learn your thought process when defending that design choice.
Great channel for system design. Highly appreciate your efforts. One question though, at around 15:55, under option1(single leader replication) you mention that for a receiver the FE needs to query the metadata service to find the leader. Since data is replicated across all nodes, read requests can be serviced by any followers right ? I agree for writes, leader needs to be sent the data.
This was the first video I'd seen from this channel. This is some next-level system design content. Way more in-depth than other videos I've seen. Unfortunately, it doesn't look like there have been any recent uploads, which is really too bad.
Yeah! But the content is so dense! I mean it more than enough
Each word in this video is a golden word. Make sure you don't skip or neglect it. Thank you so much
this is the best video for systems design I've ever watched. I listened to it at 50% speed to write down every word whereas I usually watch YT vids at 1.5x -- each sentence was invaluable.
This is absolutely the best content on RUclips on the system design topic! No "scratching the surface" bullshit, but rather very in-depth and concrete explanation on how to navigate successfully through the system design interviews. Thank you Mikhail for your great efforts! Большое спасибо, Михаил! One thing bothers me though, there haven't been any recent updates on the channel. I'm pretty sure, all the people here will appreciate and support if Mikhail decides to continue his endeavours and uploads new videos! Anyway, thanks a lot!
Normally I play videos in 1.5x or 2x. Your videos have so much information that I am afraid of losing some fundamentals if I play in 2x. Outstanding quality. Please keep making such videos.
Thank you, Debasish. Really appreciate the feedback!
Appreciate your efforts on aggregating and delivering such quality content in such a lucid manner. I don't think there is better content than this anywhere on youtube especially for system design topics. Wow ! (Y)
Thank you, Aditya. Appreciate your kind words.
@Jordan Apollo SPAM Alert
Totally agree, top quality content
I almost never comment on RUclips but this undoubtedly deserves an exception. Thank you for the superb quality content you’ve put together. I wouldn’t be surprised if this series becomes the de facto video resource for systems design and architecture interviews. Hope you keep uploading!
Thank you, Johan, for all the kind words! More videos to come.
This is the best content on system design I've ever seen. Please consider resuming the journey! We'd love to ride along!
5:10 load balancer availability/single point of failure, can assign multiple A DNS records for our domain (multiple IPS
) when we want multiple load balancers
8:00 usd cases for frontend service
9:15 request deduplocation to achieve exactly once or at most once semantics (the ack response could be lost when sending back to user, so user will retry and we don’t want to process duplicate requests that we already housed)
12:00 reusable components for other system designs
can't thank you enough for this video. All of these components are building blocks and the interviewer can dig deep as to how the requests are handled from client to server. Awesome video
Mikhail is the best. His system design videos are systematic and top notch with respect to quality and crispness. Presenting how to finish a complete design in 35 to 40 mins Wow, this is a great feat and only way for us. Prior to watching these videos my ideas and presentation is messy and dis-organized, but these videos gave me the basic sense what is expected in System Design and how to approach it. I take down the notes while watching the videos and try to apply these principles to other interview questions. This is greatly helping with my preparation. Can't thank you enough Mikhail, you are one of my best teachers.
Glad to hear that, thunrou! Thanks for sharing!
I don't think any other youtube video on System Design goes this deep into explaination. Thanks for your efforts in bringing these videos to all of us.
Thank you for summarizing precisely about what can be covered in a 40 minute time limit. Knowledge is one part which is built over learning and experience. Your video really helps to focus on structuring and expressing the knowledge in a coherent manner. Thank you.
I wish this guy was still making these videos. By far the best of the system design interview content out there (I've watched them all, lol).
13:17 Strictly speaking, using a database as a backend message store is a valid option (because database = storage engine + high level type system). The problem is that FIFO message ordering semantics, that is usually expected from queues, is not easily achievable on the top of off-the-shelf databases. Because the latter are usually designed for a different query/update patterns than it's common for queues. But some databases can handle this custom case perfectly, and some queues (Kafka) are even positioning themselves as a databases.
mysql auto increment id could be an option to implement FIFO queue. Queue name could be a secondary index, and auto increment id is a primary key.
These videos are best resource among all I have gone through. I am surprised, why this channel is not posting any more videos. Good Work and thank you !
I've watched the whole series already, thanks for the great quality content! looking forward for more
Thank you Dragoon77! Working on more videos.
wow! This is so to the point and even the duration of the video is as good as an actual interview discussion! Touched so many "must know" topics!
thank you for working on the subtitles, makes it easier to consume your good content
Sure, Rishabh! Thanks for letting me know that subtitles help. Every next video will have subtitles as well.
Thanks Mikhail. You have excellent english fluency. I am just used to different pronunciations of certain words.
I love the way you dive in every component one by one.
Thank you for the feedback, Pramod!
I bought your course. Arguably the best investment I made for system design courses so far. Thanks for putting together contents and explaining them so lucidly. I look forward to other two modules.
the course isn't available for new users :(
where is the course link?
This is the best distributed message queue system design I have seen so far. Many good concepts introduced and summarized , I feel it very helpful by using it as a guideline and read the other documents for more details such as the AWS SQS document. Looking forward to more content in the future.
Hi Jianan. Thank you a lot for the feedback!
It is full of quality content, It took me around 2-3 hours to completely watch along with preparing notes for this video. And 9 pages of notes it is, initially I thought it would be in 3-4 pages only. It's full of rich content, that I had to note everything down. Thank you. I am looking for a better way to prepare for System Design questions. With this speed, I am not sure how much time It will take for me.
Hi Mukesh. You are right, preparation for a system design interview is a lengthy process. And it greatly depends on the level you plan to apply and your background.
Just take one step at a time. First, try to learn about concepts without going too deep into each one of them. Otherwise, you will find yourself traversing a very deep graph of various interconnected concepts. Second, go deeper with every next iteration, if time allows. Third, use your daily work as a constant source of knowledge. Ask yourself how things in your project/application work. And do not stop asking yourself until you get a pretty solid understanding of a particular feature.
It is a big and a very good question you've raised. I should, probably, create a video on how to prepare, depending on how much time one's have.
@@SystemDesignInterview Thank you so much, Mikhail. I will follow these tips. Really informative.
I have been following some system design channels on youtube and this one is by far the best. Well structured, it discusses tradeoffs, solutions are clear.... In one word, AWESOME! Thank you very much.
17:08 to clarify option 2, queues are basically each a cluster in this case(each cluster contains a set of queues). Instances are the replications.
Interestingly replication for inmemory hosts/instances are handled similarly to nosql nodes
I have seen a bunch of youtubers for system design interview...this one is one of the better ones...good way of using graphics while talking instead of mundane approach of heavy talking and using a whiteboard....Great job buddy...I am gonna explore all your video now
Just the right amount of detail. Surprised it has fewer views. Shows view count is not very reliable. Thank you for the great effort
Appreciate the feedback, Manju! Thanks.
Very thorough! Really appreciate your hard work. I can tell your channel will become huge for engineering resources.
Thank you, Hyunmin. Appreciate your feedback and words of encouragement!
Best course available on the Internet.
I can’t thank you enough, I was really struggling to grasp these topics and your explanations really helped me put it all together 🙏 excellent work!
Hands down best System Design Channel on youtube. I cannot wait for more videos!
Thank you, Niko, for the feedback. Much appreciated! Working on a new video right now.
This is pure GEM!.. Amazing crystal clear explanation on Distributed computing concepts. Best tutorial till date on whole of youtube for system design prep material... Great work
This is by far the best curated content on system design
Wish I had come here before . Keep up the good work
Hi Pratik. Thank you for the feedback. And welcome to the channel!
The quality of the videos that you make are really make. Please continue making such videos.
Glad you liked it, Akshit. Thanks for sharing!
Please keep uploading! This is great! Thanks
Sure, we will. Thank you!
Just awesome ! Your approach to problem solving is very generic. Really liked it and keep posting such fantastic system design interview questions. This is the best material i have seen till date on the topic.
Thanks a lot.
Thank you for the feedback, Yash!
Hi Mikhail, excellent video on the system design course series. Very nicely presented & explained.
One of the best channel.
Thank you, Harsh, for the kind words! And for being active on the channel (actively commenting)! Much appreciated.
Summary(notes):
1. Problem statement: Producer sends data and exactly one of the consumers gets the data
2. Resolving ambiguity in the problem statement by asking questions such as scale, priority, and so on...
3. Just focus on the core set of requirements - sendMessage(messageBody), receiveMessage()
4. SLA numbers for the non-functional requirements
5. Components: LB, Control Plane(Metadata-Service), Data Plane-1(Frontend), Data Plane-2(Back-end)
6. FE: Required Cross cutting concerns such as billing, throttling, the most important - routing to Backend since the Backend is stateful and so on.
7. Metadata Service: Caching Layer for routing information and metadata ( high consistency required in case of very few writes, R/W Ratio)
8. Backend Service: API Handling Layer, Storage and so on. Since Backend has to be HA and fault tolerant as it requires a consensus service like ZooKeeper or In-Cluster and Out-Cluster management strategy.
----
Extend the above design of queue creation with queue deletion, message deletion, message replication, delivery semantics( exactly once delivery not supported because it requires 2PC) and Pull vs Push messages, security and monitoring.
---
Scalability Bottlenecks, use-case exntensability and use-case supported/limitations?
Hi Mitesh. Concise and still captures the key ideas. Great summary.
Your videos are Superb !
Most useful videos on System design.
Please start making more videos like this !
More on each component details which helps in System design :) !
Amazing video series that goes beyond high level fluff, thank you so much!
This is quality content. Really appreciate your efforts.
I am expecting you write a SD book that gives us the same amount of useful information as here. outstanding job!
I'm surprised I've not found this sooner. One of the best resources for System Design. Sadly, I think Mikhail has stopped making the content. I hope you read this and do make more awesome content! Subscribing in case you do!
Great work and Explanation . Thanks a lot. This is the best explanation and walk through to prepare for a System design interview.
Glad you liked it, Swapnil! Thanks for the feedback!
Thank you for all the hard work and such a great explanation of complicated topics. This is way superior to other paid content. I would love to see video on API design that covers how and what. For example, question that say design an API to upload photos from iOS, how do you go about it?
What are the good characteristics of an API? What are key components you need to think about while designing an API and so on.
This is more just Distributed MQ. The video covers the fundamental approaches in modern data intensive distributed systems.
Hi Ivan. Thank you for the feedback!
Thanks allot @Mikhail. Your videos are so fun and easy to watch. I feel it's one of the best specifically for system design and you sound like some Russian Pro coder to top it;) I request you to make a video about all the possible components (load balancers, CDN, etc) in a system design interview that will ever be used, because you keep using few different components for different problems. If we get to know all the components, then we too can arrive at a better solution. Thanks for the great content and keep creating new videos! 👍
Thank you for the kind words, Chirag! I have been thinking about the same for a while. And there are ideas how to address this. Just need to find more spare time to realize all these ideas ((
Very good content. Enjoyed going through the video. Thank you. Hope you continue this series
This video is great quality. I think sequential writes should have been suggested in the video. This seems to me the best way to achieve high throughput.
best system design video I had watched.
Glad to know that!
This is excellent! Looking for more such videos.
Thank you. We are working on more videos. Feel free to subscribe to stay tuned.
Just awesome...your approach to solving a system design is amazing. Great content. Thank a lot for your efforts.
Thank you, Ankit, for the feedback! Glad you liked the video!
One of the best system Design video I have watched, Awaiting more videos.
More to come! Thank you, Rahul. Appreciate the kind words.
Finally finished going through your videos. Thanks so much!
Very helpful! Another super effective way to prepare system design interviews: Do mock interviews with FAANG engineers at Meetapro.
Thank you! This covers a lot of background. One thing i feel should have been covered how strict message ordering is achieved across partitions?
Great content. Thanks a lot. Just one feedback: Would have been great had there been subtitles as I find a bit difficult to get the words.
Hi Reyaz. Thank you for the feedback! Point taken, I will try to add subtitles relatively soon.
Hi Reyaz, you can use inbuilt feature for subtitles provided by RUclips player.
Click on the icon labelled with cc while playing the video.
hope it helps until Mikhail provides the subtitles.
Thanks
Really great content and well paced delivery. Waitiing for more content.
Really comprehensive coverage of the topic! Although, would've loved to see more discussion on Asynchronous out-cluster replication. It's tricky to design, eg. what happens when you receive a get request while the data hasn't fully replicated across hosts in a cluster? can we hit all hosts in a cluster? what happens if we receive a get request when the message deletion replication is in progress etc.
This is crisp and clear. Many thanks.
Thank you for the feedback.
Thank you so much for your videos. I have watched all videos in your channel. Waiting for your distributed database video. Hopefully you are still running this channel
16:21 Question: can FE talk to the in-cluster manager instead of MS to figure out which leader to talk to?
in-cluster or out-cluster needs to be behind a facade which MS.
Great content! Thank you for making this. One thing that seems not clear (at least to me) ~min15-min17 you show the flow of the message from FE to backend node and to receiver. It is unclear how do you separate persisted information between MS (database) and in-cluster manager (ZooKeeper). Both seems to store mapping between Queue name and Leader Host. Do you really need to store this information in two places? How are they synchronized? Why would you need to keep this info in the MS in the first place? Isn't ZooKeeper enough for queue-to-node mapping?
Both options are fine:
1. When we store mapping in the Metadata service. Zookeeper is used for leader election and leader monitoring. And if leader changes, this information is propagated to the Metadata service.
2. When we store mapping in Zookeeper. Zookeeper is highly optimized for reads.
Anyway, this information is stored in one place. So that we avoid any synchronization between configuration storages and have a single source of truth.
@@SystemDesignInterview Thank you for answering this question. I had the same doubt when going through the material.
Really great content. Please keep uploading more videos!
Thank you, Narain. I surely will.
Thanks a lot for your videos! Very helpful!
I wonder if it's possible for you to have a mock interview video (e.g. you're on the interviewee side), covering things like what tools/apps would you use for real-world SDIs for better productivity, etc.
15:20 why was leader-follower option A? Why not use a loadbalancer? Why not use sharding to pick a queue, or have all machines be equal nodes, and pick a random one?
Summary of option A and B:
A uses leader to cleanup and replication
B instances are equal, but still need something to handling of each instance
For monitoring, it’s be helpful to monitor size of the queue. Also number of messages getting queued or dequeued for each host at the queue level.
Good points!
Such a great video with so much information! Many thanks!
Thanks for the video, had one suggestion on rate limiting. Token bucket is widely used and not leaky bucket.
This is amazing, thank you so much! Very detailed explanation and exactly what I was looking for.
Thank you for your great work! Please keep it up with more great content! :)
Thank you, Xiaomeng, for the feedback! More content to come.
This is awesome!! Thank you!
Glad to hear that! Thanks.
Overall great video. Speaker is very knowledgeable.
Thank you, Chicken Tikka Sauce, for all your comments. To this and other videos. Much appreciated!
Regarding how the front end service finds the leader backend nodes, you mention that this discovery would be done via metadata service. But in the in-cluster method, we actually have that information in the coordinator service (zookeeper). In this case, would the metadata service just be a thin wrapper for the coordinator service (in case of backend node discovery)?
Thank you so much for sharing these videos Mikhail. (Also, I love that you mention several times that the interviewer is there to help us, I find it delightful to have that perspective, and definitely helps during the interview)
Hi Suharto,
Thank you very much for the feedback!
Regarding your question, we can use either Metadata service or Zookeeper itself for storing and retrieving information about leaders. Please take a look at my answer here: ruclips.net/video/iJLL-KPqBpM/видео.html&lc=UgxAE6YfMUj95phbLid4AaABAg.90QChp-3ylO93AokcEr3Bu
Reall enjoy the video, I wish I could upvote multiple times. One thing missing is how to persist message into file system.
A few questions
- at 10:12 you say that "read when mesg arrives, write only when queue created". why? wouldn't you write every mesg arriving to the cache?
- metadata service is it responsible for persisting data to db other than being used as cache? if so why is backend service also doing the same?
- when you say distributed queue, you mean queue for communicating between a single producer-single consumer resides on several machine or between several "single produce-consumer" connections on several machines? if former, wouldn't only one machine be sufficient?
Hi Jm Ka,
1. Metadata service is used for storing meta information such as queues to backend service host mapping so when we create a new queue then only we need to add that info to Metadata Service persistent storage and cache as well.
2. Backend Service stores the actaul message and based on the requirements we may cache for frequeuent accessed queue to Metadata Service.
Hi Jm Ka,
Hopefully Mitesh's answer helped to clarify what is stored where. Metadata service for metadata only and Backend service for messages.
As for your last question, can you please clarify what yo mean by "several single produce-consumer connections"?
Each message lives on several machines. To achieve high availability. Simply speaking, we want to make sure that messages are not lost if a single machine crashes. Every time we store a published message, we replicate it. So, we always have several copies of the same data.
@@SystemDesignInterview Hi, Mitesh's post doesn't answer anything, it's simply reiterates stuff he heard you say.
1) was how at 10:12 for metadata service you say "read when mesg arrives, write only when queue created". Is metadata service (or cache) storing the whole queue including messages? Or is it storing only which queues go to which consumers? Either way, when a message arrives, then too it'd need to be cached in metadata service, so there has to be a write. In that case, saying ""read when mesg arrives, write only when queue created" would be wrong
2) Is metadata service only a cache or can front-end service persist messages without going through metadata service?
backend service persists messages, but it looks like in your description metadata service is doing the same too?
3) by the term "distributed queue", one could mean several things. A) you can have a distributed queue that's conceptually a single queue for only 1 producer that's generating messages for 10 consumers, but the queue is replicated and sharded on several machines for availability concerns. B) you could have a distributed queue that's multiple queues for 5 different producers, each one catering to 10 consumers (total of 50 consumers). this queue can also be called distributed. C) a distributed queue that's multiple queues for 5 different producers, each one catering to only 1 consumer (total of 5 consumers).
By "several single produce-consumer connections" I meant case (C).
Which one of A or B or C you meant by "distributed queue"?
Hi Jm ka,
1. We write to Metadata service only when we create/update queue metadata. We do not store messages in Metadata service. When message arrives, we make a call to Metadata service to get details about the queue. E.g. we may retrieve message size limit value and check if the just arrived message exceeds the max size or not. Messages are only stored on back-end service machines.
Please let me know what part of the video confused you and made you thinking we store messages in Metadata store.
2. When message arrives, front-end service needs to pick a back-end machine for storing the message. Same is true for retrieving a message, front-end needs to forward receive message request to a machine that stores messages for the requested queue. So, front-end needs to get this information from somewhere. From some persistent storage. Calling database directly is not great in this case, as there may be too many calls. This may be both slow and expensive. Metadata service helps to avoid direct calls to the database, by storing queue metadata information in memory.
3. Distributed simply means messages for the same queue are replicated and stored across several machines. There may be multiple producers and multiple consumers. Only one consumer gets the message.
Let me know if you have other questions.
@@SystemDesignInterview Hi, Does that mean the in-cluster(zookeeper) out-cluster mapping information is retrieved from the metadata service
Great content! I have some confusion regarding the queue identification.
1. In the API definition, we are only sending the message, so when the first-ever message comes, how is that message getting mapped to a queue number? For example in the slides it says a sendMessage(msg) comes for queue id =1, how does the sender know about the queue id? Similarly, when the receiveMessage() API is called, how does the receiver know which queue to get the message from, secondly there are several messages in the queue, so how do we know which message it wants to receive, and how are we deciding?
Let's say., when the first message comes around, the backend stores the data and takes care of replication, then writes the mapping in the DB. But how is this information being propagated to the receiver, that wants the message, how do they get to know about the queue id?
2. In the table shown for in-cluster management, for qid 1, the leader is A and followers are C, B. But if the queue is distributed over nodes, then how are we just having one leader node as A? Doesn't that mean we are storing the entire queue 1 in A, and the copies in the followers?
1a. Message should contain QueueId.
1b. API should be queue.ReceiveMessage() ; Queue object knows about queue_id and sends in either every poll request or is tied to tcp/grpc/websocket connection.
1c. Messages are received from queue in kind of FIFO order. So, client sends last Message id or Sequence Number and server sends SequenceNumber+1 th message.
1d. Client knows queue name and that should be able to give them queue id. It can be either hash of "queue_name" Or they ping Frontend service to get QueueId for a QueueName.
2. A distributed queue does not mean partial data on different nodes. It means full copy of data on all nodes. One of the node can only currently write -- this node is called Primary node. This is done so that even if one machine goes down for ever, full copy of data is available in other machines. This gives high availability/durability in case of failures.
keep up the good work! please upload more system design videos!
It would be helpful if you also give a brief intro to RabbitMQ, Kafka and Kinesis/SQS. You talked about SQS briefly, that was really appreciative!
Hi Yetesh. Sounds like a topic of its own. Let me add this to the TODO list.
10:31, why does the architecture show a single DB for A-Z records, doesn't it defeat the purpose of having shards across MS. I would think that each MS manages the shard it is responsible for ?
Brilliant content! Please start uploading again!
Please make more videos..ur videos are gem
any reason that we don't have more content uploaded here? is the author busy?
Hey Jordan
It’s almost 2 years we are waiting for your videos. I hope you’re fine?
Thanks for the great content. Can you please talk about which choice of architecture (1, 2 or 3) you would make for the Metadata Service? And why? And please explain your comment that the datastore for MS does not need to be strongly consistent?
Great video, very in depth
I have a question concerning option b for the backend service architecture (Small cluster of independent hosts)
The frontend calls the meta service to find out the instance responsible for the queue yet calls a random instance. If it’s going to call a random instance why call the meta service?
In the backend storage design, Option B, one node in the pool of the backend hosts is responsible for distributing messages to other hosts in the pool. The downside with this approach as I see is that the client(sender Front end) has little idea about how many hosts the message is actually distributed to. What happens if the receive call selects a host which does not have the message? Wouldnt it make more sense to have a quorum based read and write approach at the front end service layer. Where it sends a send request to x hosts and wait for x acknowledgments and receive request is sent to y hosts and wait for y responses. As long as x+y > total hosts in the pool a consistent read is guaranteed. Of course this is assuming consistent reads are needed and strict ordering is needed which adds to latency. Also a little unclear on the role of metadata service here? Specifically what information does it store if there is another out cluster manager for hosting information about queue to cluster mapping.
I guess it really depends on the semantics of the queue. Ex: Is FIFO guaranteed etc
This frontend service looks more like a backend service to me and @15:55 ,does FrontEnd recieve a message from queue, and then communicates to Backend / Message Service (blue)?
MS - Metadata Service
in the minutes of 16:10 how do we know what queue ID to assign for each message ?
These are really nice videos with quality content. Suggest you to slow down a bit. Just a doubt:
in 5:58 you talk about using VIP partitioning and spread it to multiple data-centers. With this should the Meta-data store and backend-store be replicated in each of the data centers. Because due to dns load balancing the request can go to any load-balance and the data-centers that the producer api hits( sendMessage() ) and the consumer api hits ( recieveMessage() ) can be different. Can you pls shed some light on this. Thanks!
Awesome video. The only thing that was a bit confusing for me was the part about in-cluster manager (zookeeper) - It wasn't clear if zookeeper is in fact the Metadata service or an additional component (along side MS).
Yeah I was confused too. I posted a comment below, happy to discuss more.
Hi Michael. Thanks a lot for the feedback!
Here I left my view on why separation for out-cluster manager approach (multiple clusters) makes sense: ruclips.net/video/iJLL-KPqBpM/видео.html&lc=UgwD2gh8ozvKz1wMqId4AaABAg.99gLjSiA1G79BLjjputJT6
For the in-cluster manager approach, we can indeed use a single component. And the way Kafka uses Zookeeper proves this. As Zookeeper is "especially fast in "read-dominant" workloads." (from the official Zookeeper site).
Although, I still prefer to separate these components for the in-cluster approach as well. There are many arguments in favor of one approach or another.
Thanks for such a great content.
Thanks for such a great comment!
Thank you for great quality content. Excellent explanation, I can't miss single word.
Why the series is stopped? Any other resources would you recommend?
Thanks for sharing the design. May I ask a question?
As you mentioned at 1:22 of the video, in case of queue, the message is received by one and only one consumer. Does it mean, we should create a queue for every consumer?
Great video, thanks for doing these. Can you please explain why we need a FE component? Initially I thought it was to design a distributed message queue, the ones used by the backend services, like the one that you had drawn in your other video: System Design Interview: Step by Step Guide. Or is this a question about how to design a chat appication? And then my last question is, can we combine VIP with load balancer into one component, the API gateway? Thanks!
I have the same confusion. Don't know why the front-end is needed.
Big thanks for the videos, great material !
Really great content. I have one doubt. In the out cluster management option, let's say we split each queue into multiple partition across multiple clusters, and each partition is being handled by separate clusters with replication of data in all the nodes inside the cluster. What if an entire cluster goes down? How will we ensure durability of the message belongs to the partitions managed by that cluster.. Please help me to resolve the doubt.
Great video, but I think it should cover even more low-level details on how messages are stored in memory and retrieved using offset/invisible flag.
Can you please talk why you would use log files to store the data rather than the database? I have an idea but I would like to learn your thought process when defending that design choice.
Great channel for system design. Highly appreciate your efforts. One question though, at around 15:55, under option1(single leader replication) you mention that for a receiver the FE needs to query the metadata service to find the leader. Since data is replicated across all nodes, read requests can be serviced by any followers right ? I agree for writes, leader needs to be sent the data.
Yes, that can be done. Followers can be used to honor reads.