I have watched multiple videos on system design but the content you have is exactly what is needed to crack the interviews. You are among the best on youtube in terms of content !
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
The improvement what I see in your videos is you keep everything drawn already on the board rather drawing it on the go. That would have been good as to know how you think through the whole system and how you approaching step by step. Also one more thing is the diagram could be more organized so when you talk you run through any flow it should be one functional flow from start to end rather than picking random components.
That would make some of his 1-hour videos 3-hours length though... When everything is prepared he is able to cover more aspects and go more in-depth in shorter time. Anyway, I am not sure if we will see new videos from him.
It's not like I am trying to make some comparisons here but I usually prefer watching multiple videos for the same design topic and I can easily say that I find Sandeep's tutorials the most comprehensive and lucid at the same time. Awesome job there Sandeep.
I have my first interview tomorrow and i was so scared, thanks to your videos i no longer feel like that and i feel like im actually capable of showing of what i learned so far in my career tomorrow. THANK YOU
Great video as always. I found myself liking the videos in which you draw the system in real time. It gives a much better idea of a system being built to solve multiple levels of problems step by step. It also keeps the viewer more focused on the piece being worked on.
This is the very comprehensive and clear explanations of the concepts, I have seen so many videos in platforms like udemy, linkedin learning, Oreilly but I found this explanation and design best for the ecommerce platform.
I think Wish List and Cart service should not be associated with Search service rather it can be directly connected to user pages once he/she is logged in.
Vivid explanation. I would add that where you run the purge and archive what I have seen a heavy use of asynch flows so some kind of queue in between which would delete the data through processing service but dont talk directly with historical service, instead generate all these order events and put them into a queue and the listener on the other end would talk to historical service and finish the rest of the process. Since purge may pull millions of records so expecting archival service to deal with order processing and historical at the same time may cause frequent failures. Very nice content. Thank you.
One more point - when redis sends the expiry callback to order taking service we can also put a check there to first check the status of the order. if order is placed then ignore the request. Deleting from Redis when payment is confirmed is also good but safeguarding at both ends would be nice in case we fail to delete the record from redis.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
@@aashishsawant3150 mongo-db is used when you have unstructured data which can have varying attributes yet you need to query them with complex params. For example, you may want to find a shirt of size M and color crayon and has a chinese collar etc. how inventory service and elastic search talk to each other: They don't have to.
@CodeKarle Nice explanation. Since the order, payment, and inventory are managed by separate microservices, we may need distributed transactions here. Thinking about cases like we reduced the inventory but the order service failed to persist the order. It would be great to discuss this issue along with different distributed transaction algorithms (Paxos, 2PC, 3PC, Saga etc) in your next video.
Correct, SAGA is way forward here. 2PC and 3PC are quite slow in real world, besides making this process synchronized suffers from late response to the client. A better way in SAGA suggests that we provide an immediate response let the SAGA complete. Once completed or rolled back then confirm the order.
This has been a clear vision for the process with multiple DB depending on the what type of data we are getting saved. It helped me a lot. I have designed one solution. If you have linkedin or similar can we connect. Just for a clarification, like MongoDB, Cassandra and Analytics tool can't we use any ERP based backend like SAP, ARIBA for purchase flow to make it more easy and smoother. These already have best Load balancing. I am a SAP consultant and looking for the similar solution that i have seen for multiple industry in my project experience.
Thanks buddy for such a nice explaination. Since this is Amazon and hence global presence, I had few questions which may be asked in an interview 1. How is the user service Db synched , e.g. user is in India however now he went to US and access US website. Will there be a master Db which will have info about all Users or how will the system sense where to fetch user info from ? 2. If we say the DBs of all regions will sync with some Master DB, how will this sync happen ? 3. Will there be a Load Balancer infront of REDIS (wherever its used ) ? 4. Infact there can be a LB infront of every service component, if not then how are the requests routed as there could be multiple servers running that service ( e.g. Cart Service) ? Could you ( or any other user) please help to provide some guidance on this ? Thanks in advance.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
1) I think Wishlist and cart service flow should not go via Search Service. What do you think? 2) Spark ml data should get stored in database ( druid/cassandra) to get consumed by recommendation service
You're right, the APIs to the services you meantioned would be independent anyway, just that the wishlisting/adding to cart usually is done by the users post search results are shown. That's why it follows the search results in the user journey. Functionally, they are totally independent. The recommendation logic can run as a Spark job which then then store the data in any datastore through Recommendation Service. The same service would then consume the data written in that data store to power various recommendation based functionalities.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
sir, why have you stopped uploading videos, we all are enjoying your knowledge so much! Please can you upload more of such videos, it will mean a lot to all of us.
All your videos are excellent . Only issue is you are standing infront of the board which contains the architecture. You can stand on the side of the board so that viewers get a clean view of the architecture diagram.
Great explanation and well organized content flow in the video. Nicely covered many components of system design. Thanks a lot for creating this video. .
This is awesome, very granular. I love your videos. Suggestions: 1. I am not able to take a perfect screenshot of the whiteboard, if you can show video like it's the only thing in the screen for like 3 to 4 seconds, it will be very helpful. 2. Checkpoints in the video, so that we can directly go to the specifics. Very much thanks Sandeep for creating such great videos.
Thanks!! You can get some of the screen pics over here, in the individual descriptions: www.codekarle.com/ Not everything is there, but you'll still get some diagrams. Checkpointing is a good idea, we'll try to do that.
Sandeep... design a Recommendation System and designing a distributed key value store would help... Possible to take these up in ur upcoming videos?? BTW.. every video is awesome Sandeep.. best System design videos I have seen so far... very clear and not over the top, very precise yet very detailed.. Awesome work Sandeep..
Best explanation. Though i have one doubt for "USER PURCHASE FLOW" Instead of "ORDER TAKING SERVICE" and "ORDER PROCESSING SERVICE" can't we just have one "ORDER SERVICE" (which will do 2 things take orders and view live orders) as it seems too much of separation of concern OR is it done to segregate READ and WRITE traffic? Also let "ARCHIVAL SERVICE" talk to "OMS MYSQL DB" for getting orders which are in TERMINAL State. What are your thoughts?
Just 1 suggestion, instead of taking these big designs, you can choose smaller things and make a series of videos, then 1 video to just stitch it. The issue I see is that we are going into some things in deep whereas some other important things seem to be missing
Its great explanation of system. I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory & Order databases for transactions and Cassandra for historical based queries.
Thank you. Very quality design, with most of components, edge case cover. Best system design material with real life issue/functionality. One feedback, it would be great if you can show yr whiteboard with diagram without you in between so that one can take screen shot and keep it for future reference. Thank you very much.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
Great video as always. Thanks for this as it help developing thought process to architecting solution. One thing, no detail as about the Inventory service like from where it data get populated. As we have item service to keep product details. It will great if you put your thought on this to understand the flow. Inventory service is one of the service.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
Great video. Can you please do a follow up video covering OMS system built top of this architecture. Can you also discuss some tradeoff and improvement which can be done. Ex: scalability wise? Thanks.
@@codeKarle thank you. Can't wait to see your follow in-depth design. As always great content. One suggestion: can you also discuss future improvements and tradeoffs of the design and architecture for upcoming videos. I think, that's important to understand as well. Ex: If we go serverless by using lambda, stepfunction, etc
At 18:59 Is it like the inventory table will be accessed and updated by only one transaction at a time?? if its so then how can multiple orders be placed during high traffic conditions?? How will we achieve parallel processing then?
Very clear and well explained all the features.. thanks for sharing, I appreciate your efforts. Could you please make a video on how to design Database schema for e-commerce app in details?
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
1. I dont think we need to store items in mongoDB. we can store all the items in just elasticsearch and that can be our source of truth. The Item service can also be built on top of elasticsearch only. There won't be a lot of updates on the products added so we don't have to do reindexing in the elasticsearch. So, for the required use cases, elasticsearch should be sufficient. 2. cart and wishlist service should be interacting directly with the load balancer. once we get the product id we should be able to directly call the cart service. we should not call the search service for adding items to the cart. 3. what if the order service taking service itself fails before confirming an order. How can we handle those scenarios? 4. do we really need to create created state in db for order service? Is it because we want to see these orders as cancelled orders in my past orders? Will this state be applicable in a food delivery app like swiggy? Thoughts?
Thank you so much for this video! Appreciate if you also share a transcript of the video in the description. It'll help keeping it handy for reading through the key concepts.
It's very nice and clean approach. Thanks for all your effort. i would like if you can create a catalog management system video which can cover the master data management for product as admin.
Thanjs for sharing this...however I feel that instead of havign everything drawn out if you had drawn each component at a time will be been better. It would have made clear your thought process and will have been less overwhelming
Hi Sandeep, Thanks for the amazing videos. They have been very helpful. Would love to see more videos coming like Designing Dropbox, Pastebin, Web Crawler etc & system design patterns.
How is wishlist service db partitioned? Can’t be based on geography as that may put a lot of load on one node and rural vs urban area issue. Can’t be based on a product as then for the same user to get all the info multiple nodes will be hit which is not a good design. IMU we may be able to do so based on the country + user. In that way we may not need to scale all the data servers belonging to all countries. Also we may small countries with population in a range all together.
Happy Learning Indeed Sandeep!!! Lot of good points discussed - you talk about choice of components right in the context of design than suggesting a read up. It is also better than a few paid subscription tutorials. One suggestion: I liked the write up on codekarle describing system design which you traded for closed captions/subtitles. Can you add them on your website? Easier for a 2nd go over...
Thanks for sharing this video. Really appreciate the clarity of thought in your explanation and flow of the design.
Glad you enjoyed it!
I worked at Flipkart and the architecture described here provides good insights into what we do. Good one. We're more on HBase than Cassandra though.
That's great to hear!!
@codekarle how can we implement the discount that Flipkart provides that vary time to time
Can i get your contact info ???
@@rahulsinghai3033 rule engine 🤔
I have watched multiple videos on system design but the content you have is exactly what is needed to crack the interviews. You are among the best on youtube in terms of content !
Thanks Abhimanyu!!
Glad to hear this.
Do spread a word about us amongst your friends. It helps everyone :)
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
I work at Ozon (Russian equivalent of Amazon) and yes, our architecture is quite similar
Do you have idea about How item service communicate with Inventory service ?
Instead of Item service, you can just use inventory service I think@@aashishsawant3150
The improvement what I see in your videos is you keep everything drawn already on the board rather drawing it on the go. That would have been good as to know how you think through the whole system and how you approaching step by step. Also one more thing is the diagram could be more organized so when you talk you run through any flow it should be one functional flow from start to end rather than picking random components.
Anyone has idea about How item service communicate with Inventory service ?
That would make some of his 1-hour videos 3-hours length though... When everything is prepared he is able to cover more aspects and go more in-depth in shorter time. Anyway, I am not sure if we will see new videos from him.
It's not like I am trying to make some comparisons here but I usually prefer watching multiple videos for the same design topic and I can easily say that I find Sandeep's tutorials the most comprehensive and lucid at the same time. Awesome job there Sandeep.
Thanks Apoorv!
I have my first interview tomorrow and i was so scared, thanks to your videos i no longer feel like that and i feel like im actually capable of showing of what i learned so far in my career tomorrow. THANK YOU
All the best for your interviews!
This is at next level. I am making notes of all your videos and recently cracked a company. My best wishes to you brother :) :) God bless you :) :)
Bro I am also making notes , can we connect on linkedin
Great video as always. I found myself liking the videos in which you draw the system in real time. It gives a much better idea of a system being built to solve multiple levels of problems step by step. It also keeps the viewer more focused on the piece being worked on.
Do you have idea about How ItemService communicate with InventoryService ?
Having worked in a super large system for 11 years (Groupon) I give this overview a 5 stars.
I really liked the breakdown on how to lock items in inventory and how to deal with expired orders.
Do you have idea about How itemService communicate with InventoryService ?
Videos are good and intensive. Also please show rough estimates - traffic estimate, memory estimate, storage estimate etc
This is the very comprehensive and clear explanations of the concepts, I have seen so many videos in platforms like udemy, linkedin learning, Oreilly but I found this explanation and design best for the ecommerce platform.
I think Wish List and Cart service should not be associated with Search service rather it can be directly connected to user pages once he/she is logged in.
You speak to common man! Really knowledge booster. Thanks you :)
One of the best system design playlist out there. So underrated!
Suggestion - Please start with a brute force way to design a system, it gives more confidence to one
Vivid explanation. I would add that where you run the purge and archive what I have seen a heavy use of asynch flows so some kind of queue in between which would delete the data through processing service but dont talk directly with historical service, instead generate all these order events and put them into a queue and the listener on the other end would talk to historical service and finish the rest of the process. Since purge may pull millions of records so expecting archival service to deal with order processing and historical at the same time may cause frequent failures. Very nice content. Thank you.
One more point - when redis sends the expiry callback to order taking service we can also put a check there to first check the status of the order. if order is placed then ignore the request. Deleting from Redis when payment is confirmed is also good but safeguarding at both ends would be nice in case we fail to delete the record from redis.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
@@aashishsawant3150
mongo-db is used when you have unstructured data which can have varying attributes yet you need to query them with complex params. For example, you may want to find a shirt of size M and color crayon and has a chinese collar etc.
how inventory service and elastic search talk to each other: They don't have to.
Buddy your knowledge level and skills are unmatchable. Keep making these videos.
Thanks Deepak! Do spread the word about the channel :)
first person who doesn't teach just for interview purpose but in general how systems are designed, really appreciate you :)
@CodeKarle Nice explanation.
Since the order, payment, and inventory are managed by separate microservices, we may need distributed transactions here. Thinking about cases like we reduced the inventory but the order service failed to persist the order. It would be great to discuss this issue along with different distributed transaction algorithms (Paxos, 2PC, 3PC, Saga etc) in your next video.
Exactly my thoughts. As Sql doesn't provide distributed transactions, the statement made in video is little misleading
Right..Also they whole order taking journey is synchronously spanning through multiple microservices. Would that not block the customer?
Archit, Do you have idea about How ItemService communicate with InventoryService ?
Correct, SAGA is way forward here. 2PC and 3PC are quite slow in real world, besides making this process synchronized suffers from late response to the client. A better way in SAGA suggests that we provide an immediate response let the SAGA complete. Once completed or rolled back then confirm the order.
This has been a clear vision for the process with multiple DB depending on the what type of data we are getting saved.
It helped me a lot. I have designed one solution. If you have linkedin or similar can we connect.
Just for a clarification, like MongoDB, Cassandra and Analytics tool can't we use any ERP based backend like SAP, ARIBA for purchase flow to make it more easy and smoother. These already have best Load balancing. I am a SAP consultant and looking for the similar solution that i have seen for multiple industry in my project experience.
Crystal clear thought process and explanation too. Thanks for the excellent video.
Best system design video from all what I have watched. Thanks for making this!
still go through your videos regularly to brush up/prep for interviews.
thank you so much for these
It was such a clear explanation. I couldn't have understood it more from anywhere else. Thank you so much for the content!!
Thanks buddy for such a nice explaination. Since this is Amazon and hence global presence, I had few questions which may be asked in an interview
1. How is the user service Db synched , e.g. user is in India however now he went to US and access US website. Will there be a master Db which will have info about all Users or how will the system sense where to fetch user info from ?
2. If we say the DBs of all regions will sync with some Master DB, how will this sync happen ?
3. Will there be a Load Balancer infront of REDIS (wherever its used ) ?
4. Infact there can be a LB infront of every service component, if not then how are the requests routed as there could be multiple servers running that service ( e.g. Cart Service) ?
Could you ( or any other user) please help to provide some guidance on this ? Thanks in advance.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
Thoda khud se bhi doondh le bhai
Great content and well-organized flow in the video. Thanks a lot for creating this video.
Best tutorial I have seen so far on this topic. Thank you so much!
You deserve a like, subscribe share.
Honestly, explained such a complex system in a very short time precisely and clearly
1) I think Wishlist and cart service flow should not go via Search Service. What do you think? 2) Spark ml data should get stored in database ( druid/cassandra) to get consumed by recommendation service
You're right, the APIs to the services you meantioned would be independent anyway, just that the wishlisting/adding to cart usually is done by the users post search results are shown. That's why it follows the search results in the user journey. Functionally, they are totally independent.
The recommendation logic can run as a Spark job which then then store the data in any datastore through Recommendation Service. The same service would then consume the data written in that data store to power various recommendation based functionalities.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
Thank you so much for this, also pls make more videos. The quality of your talk is just too good not to be passed on to others.
sir, why have you stopped uploading videos, we all are enjoying your knowledge so much! Please can you upload more of such videos, it will mean a lot to all of us.
Awesome video. Really like your style of explaining the design. Seems very natural and incremental in approach and understanding.
That's great to hear!! Thanks for the kind words :)
Thanks for explanation .In all your videos you explain it so simple even the complicated topics with attention to details👍
crisp explanation and covered all aspects
All your videos are excellent . Only issue is you are standing infront of the board which contains the architecture. You can stand on the side of the board so that viewers get a clean view of the architecture diagram.
Great explanation and well organized content flow in the video. Nicely covered many components of system design. Thanks a lot for creating this video. .
The videos are spot on. Usually on other videos there are ambiguity in design. Your design stresses on what exactly needs to be done :) Great content!
This is awesome, very granular. I love your videos.
Suggestions:
1. I am not able to take a perfect screenshot of the whiteboard, if you can show video like it's the only thing in the screen for like 3 to 4 seconds, it will be very helpful.
2. Checkpoints in the video, so that we can directly go to the specifics.
Very much thanks Sandeep for creating such great videos.
Thanks!!
You can get some of the screen pics over here, in the individual descriptions: www.codekarle.com/
Not everything is there, but you'll still get some diagrams.
Checkpointing is a good idea, we'll try to do that.
Sandeep... design a Recommendation System and designing a distributed key value store would help... Possible to take these up in ur upcoming videos?? BTW.. every video is awesome Sandeep.. best System design videos I have seen so far... very clear and not over the top, very precise yet very detailed.. Awesome work Sandeep..
Best explanation. Though i have one doubt for "USER PURCHASE FLOW"
Instead of "ORDER TAKING SERVICE" and "ORDER PROCESSING SERVICE" can't we just have one "ORDER SERVICE" (which will do 2 things take orders and view live orders) as it seems too much of separation of concern OR is it done to segregate READ and WRITE traffic?
Also let "ARCHIVAL SERVICE" talk to "OMS MYSQL DB" for getting orders which are in TERMINAL State.
What are your thoughts?
You have explained the CAP theorem so easily which was really challenging to understand. Kudos!!! Keep up the good work.
Just 1 suggestion, instead of taking these big designs, you can choose smaller things and make a series of videos, then 1 video to just stitch it. The issue I see is that we are going into some things in deep whereas some other important things seem to be missing
Brilliant and clear explanation.. especially appreciate the reasoning behind the DBs etc.. thanks for sharing
Superb explanation, Thank you so much for nice detailing, plss keep on posting more in this era. Thanks
That's really awesome. Thanks, sir for sharing this video with us. Love from Bangladesh .
Its great explanation of system. I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory & Order databases for transactions and Cassandra for historical based queries.
Prashant, I have also the same question. If you got answer could please explain to me ?
Thank you. Very quality design, with most of components, edge case cover.
Best system design material with real life issue/functionality.
One feedback, it would be great if you can show yr whiteboard with diagram without you in between so that one can take screen shot and keep it for future reference.
Thank you very much.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
Nice content and clear explanation. Only one thing that was make me panic during whole video was sound quality. Voice is too low.
Very nice one! I literally liked and slept at the same time. Appreciate it 😎😎
I really like how you go into the details of different components - amazing work!
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
Great video as always ! very clear thanks ! only one point of improvement if you can use a better mic as sound clarity is not the best
So many use cases covered, awesome design and explanation. Thanks mate!
Great job! There was clarity right throughout
Great video as always. Thanks for this as it help developing thought process to architecting solution. One thing, no detail as about the Inventory service like from where it data get populated. As we have item service to keep product details. It will great if you put your thought on this to understand the flow. Inventory service is one of the service.
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
I really enjoyed the way you explain things...simple and effective👏🔝
My kind regards from Egypt.
Great video. Can you please do a follow up video covering OMS system built top of this architecture. Can you also discuss some tradeoff and improvement which can be done. Ex: scalability wise? Thanks.
Sure, we'll try to make that.
@@codeKarle thank you. Can't wait to see your follow in-depth design. As always great content. One suggestion: can you also discuss future improvements and tradeoffs of the design and architecture for upcoming videos. I think, that's important to understand as well. Ex: If we go serverless by using lambda, stepfunction, etc
Sandeep, Excellent .... Thanks very much...THis is a very intuituve design I have ever
seen...its pretty much covers almost all details....
At 18:59 Is it like the inventory table will be accessed and updated by only one transaction at a time?? if its so then how can multiple orders be placed during high traffic conditions?? How will we achieve parallel processing then?
I really like your videos! Super informative and easy to understand. Thank You!
This is what I was looking for, really helpful video bro, thanks a lot for your effort
You are amazing, superb explanation and with excellent pace
This is a gem of a video. Learnt a lot. Thank you
Beautiful & clear explanation. Thanks for this video !
Very clear and well explained all the features.. thanks for sharing, I appreciate your efforts.
Could you please make a video on how to design Database schema for e-commerce app in details?
Shouldn't output of "Spark Cluster" be directly stored into Cassandra? How would "Recommendation System" know when to talk to "Spark Cluster"?
great video, Just the right amount of information, thank you!
I want to know one thing. In which kind of use cases item database mongo-db will be used? as We have already search engine DB for searching items, inventory ? how inventory service and elastic search talk to each other
Thanks for nicely explanation of each component in detils.
Wow! This is very well explained. Thanks!!
1. I dont think we need to store items in mongoDB. we can store all the items in just elasticsearch and that can be our source of truth. The Item service can also be built on top of elasticsearch only.
There won't be a lot of updates on the products added so we don't have to do reindexing in the elasticsearch. So, for the required use cases, elasticsearch should be sufficient.
2. cart and wishlist service should be interacting directly with the load balancer. once we get the product id we should be able to directly call the cart service. we should not call the search service for adding items to the cart.
3. what if the order service taking service itself fails before confirming an order. How can we handle those scenarios?
4. do we really need to create created state in db for order service? Is it because we want to see these orders as cancelled orders in my past orders? Will this state be applicable in a food delivery app like swiggy?
Thoughts?
This design was so descriptive! Thanks for sharing!
Thank you for sharing, I've learnt a lot from you :)
Thanks for such detailed and good explanation
Great video and thank you for explaining all the important functionalities.🙂
Thank you!
Wow.. e-Commerce system is so complex..
Very helpful video. Thank you so much.
Thanks for your awesome videos, really appreciate the effort. Please create a video for the Google Drive kind of service also.
Thank you so much for this video! Appreciate if you also share a transcript of the video in the description. It'll help keeping it handy for reading through the key concepts.
Thank you for your work, great job 😌
It's very nice and clean approach. Thanks for all your effort. i would like if you can create a catalog management system video which can cover the master data management for product as admin.
Thanjs for sharing this...however I feel that instead of havign everything drawn out if you had drawn each component at a time will be been better. It would have made clear your thought process and will have been less overwhelming
Great content but easy to understand, Thanks codeKarle.
Great explanation. It's really worthful to watch.
Hi Sandeep, Thanks for the amazing videos. They have been very helpful. Would love to see more videos coming like Designing Dropbox, Pastebin, Web Crawler etc & system design patterns.
fantastic video v clear simple detailed.
Thanks!! Glad you liked it!!
Thank you for the clear/detailed information!!
Glad that it was helpful 👍
awesome ! Thanks for explaining it with so much clarity.
Thanks for making this video. Detailed explanation!
great explanation! thanks a lot
Your videos are really amazing!!Thanks a lot for making them.
Great design and awesome explanation of each component
This is really so much helpful
Great explanation and well organized content flow in the video. Thanks!
it is really impressive. Helped me a lot in system design.
One request is that please make a video on movie ticket booking system (BookMyShow)
How is wishlist service db partitioned?
Can’t be based on geography as that may put a lot of load on one node and rural vs urban area issue. Can’t be based on a product as then for the same user to get all the info multiple nodes will be hit which is not a good design.
IMU we may be able to do so based on the country + user. In that way we may not need to scale all the data servers belonging to all countries. Also we may small countries with population in a range all together.
Awesome explanation.
Happy Learning Indeed Sandeep!!!
Lot of good points discussed - you talk about choice of components right in the context of design than suggesting a read up.
It is also better than a few paid subscription tutorials.
One suggestion: I liked the write up on codekarle describing system design which you traded for closed captions/subtitles. Can you add them on your website? Easier for a 2nd go over...
Thank you so much sir!! So helpful and detailed, could you please do a video on how to choose what database to use?
thanks for sharing this, very helpful