Best LLD video I’ve seen so far, great work! As a feedback I would like to say it would be really great to quickly show the class diagram of the design at the end of the video. It would be a great addition for proper understanding and summary!
@snehachauhan94216 ай бұрын
Your system design explanation is best among all the other youtube channels I've seen so far. The way to you explain is so precise and clear, and there is no confusion throughout the video You actually explain how to approach a complex problem step by step without making it complex. Bestttt!!!
@amansingh16613 жыл бұрын
"And so on and so forth" is the major stress release point :)
@shubhamsrivastava19722 жыл бұрын
Good explanation however I would suggest some of my inputs - 1. ATM should not have BankService dependency, it should be inside the Bank class 2. Similarly the factory class should take Bank as an input and return the corresponding BankService 3. ATM class should have a Start() or a similar method that is gonna initiate any transaction by fetching the CardInfo, and from CardInfo fetch the Bank, and from Bank it should fetch the BankService following which it should call the ExecuteTransaction() of the bank service. PS - This is just my observation
@abhinavrastogi53102 жыл бұрын
Yes, that makes more sense and fits the design well. Here, we can follow strategy pattern as well (composition over inheritance concept) by Creating BankService which BankA and BankB concrete classes can implement and then we inject the dependency in Bank class via constructor.
@radhikautsav24872 жыл бұрын
@@abhinavrastogi5310 Hey could you elaborate a bit further please? The constructor part specially, it would be really helpful, thanks!
@lakshaychawla782 жыл бұрын
Really appreciate the efforts you are putting in to make it and i would like to congratulate for these worthy videos. Just as a suggestion- the way you introduced the videos of Hotel and Library Mgmt System by creating Part 1(req +. usecase diag) and Part 2(coding), it puts more emphasis and gets wired in mind :) Also, why not create it for other systems like food delivery, cab service, payment svc etc. Also, System design problems.
@rahulsharma50304 жыл бұрын
Awesome Video!! You made it looks like very very simple.You are teaching us something unique.Thanks. I need some clarifications : 1.CashDispenser should have method to load Cash also?The bank can load cash into ATM by using this. 2.Why do customer needs BankService bankServiceObj ?Isn't it job of ATM? 3.Why do we need to store Bank object in card?We should store complete object only if we think it makes sense.But here i think we should have only bank Identifier like bank ID/Name to which it belongs,instead of complete bank object. 4.How will ATM access BankServiceFactory?Because each time ATM operation is called,we need to call BankServiceFactory to get BankService Object.So do we need to put BankServiceFactory also in ATM class? Its a long list of doubts:).I hope you take take time to help me.Thanks in advance
@teenthofabud3 жыл бұрын
Why does Customer class has a direct reference to BankService? Shouldn't customer class be a simple POJO in nature and free from any business logic within itself?
@harshitbhagat55411 ай бұрын
Great explanation and design. Would request to add UML diagram as well and explain that bit for 2-3 minutes.
@rajeshg35702 жыл бұрын
This is very nice. I've couple of comments though - 1. It would have been nice if you have details around the DB design and tables.. 2. It would have been better if you can slow down little bit when explaining the logic/intuition behind defining each class. and also In the 'Transfer' class - I think it makes more sense to have the destAccount field type as 'Account' instead of 'String'
@sandeep56753 жыл бұрын
Superb explanation and design. Really appreciate your effort
@arunbhati14174 жыл бұрын
Please upload a video on Job Schedular and Meeting Scheduler. Please. Thanks for the efforts.
@alokch0073 жыл бұрын
It would be really helpful if you can explain database entities corresponding to these java classes.
@ganant23 Жыл бұрын
no UML diaagram, I recommend starting with that first so beginners can coonect the dots. Good video overall
@cactusbee84742 жыл бұрын
This was really great video and the flow of the video is easy to remember. Can you also make a video on lld design a cache with LRU. Pls.
@fb_a2 жыл бұрын
But with reference to base class we can access only it's properties and it's/overriden methods not the child object one's. Liskov Substitution Principle fails, isn't it?
@sasanknvs56032 жыл бұрын
I have the same question with respect to the Transaction class and its subclasses. How are we going to know what kind of transaction is it from the Transaction base class ?
@HimanshuSharma-fl1md4 жыл бұрын
Doing a great job... please make video on parking lot design
@SoumyajitBhattacharyay4 жыл бұрын
Yes i am done with the code for parking lot. Will be uploading it very soon
@SoumyajitBhattacharyay4 жыл бұрын
Hi the patking lot video is out!! kzbin.info/www/bejne/jGqxdoKCpdlmqsk
@manabendranathsaren28664 жыл бұрын
Doing great, a useful youtube channel
@SoumyajitBhattacharyay4 жыл бұрын
Thanks a ton
@kaushikg19963 жыл бұрын
Loved the content. 👌
@aggu903 жыл бұрын
one Query why we are having Bank Details in CardInfo object? Bank details can be like name but why List? what adv we are getting with this.... Waise as usual Msst video.. Ek Elevator design pe bhi bana do bhai bahut jagh puch rahe hai ;)
@ShaanRoyal4 жыл бұрын
you missed the cheque class . .clear & crisp explanation by the way . . (y)
@amitagrawal46604 жыл бұрын
Simplest explanation :) One question: Is writing API's sufficient for interview or we need to also draw Database diagram? Also, please create video for Elevator Design as well
@krishnarajyadav39533 жыл бұрын
Hii , Thanks for the video . Very Helpful. I have one doubt : Why we are extending Deposit in CashDeposit and ChequeDeposit , shouldn't we need to extend Transaction in both as Transaction contains all the info just as Transfer class ?
@palakjain25052 жыл бұрын
why is dispenseCash() not part of ATM class? Why did you make a separate class for it?
@shasisoft Жыл бұрын
We can use SBI atm to swipe any bank atm card and withdraw money right? So, if we are hardcoding BankA, BankB, BankC in our design how can this be scalable? If there is a new bank established recently, how can it support this new bank's atm card?
@Nishant05712 жыл бұрын
very helpful content. Can you upload LLD for some finance app like cred, ETMoney, Razorpay
@akshaygaikwad37932 жыл бұрын
Is it necessary to have the BankService inside customer. It already has the CardInfo obj ?
@sushantkumarrai46823 жыл бұрын
please make a series on design patterns
@rahulsharma50303 жыл бұрын
Account class should also have customer, as its a common case, given a account which customer it belongs to
@umber31174 жыл бұрын
Nice and thanks for sharing. Can you please add a class diagram also?
@kunal-gd1xp3 жыл бұрын
Is this LLD or machine coding ??? Plz reply soumyajit bhai....
@satyajeetkumarjha14822 жыл бұрын
Why no one gives a basic working code for lld ?
@rahulsharma50303 жыл бұрын
chequedeposit and cashdeposit are transactions or slots? You put in ATM class,seems that these are slots.But when u extend transaction, then these are transaction.Please update it correctly.lt.Its confusing.
@PawanKumar-xx3yy4 жыл бұрын
Please make video on Logger desing.
@rahulsharma50304 жыл бұрын
if u pass only Transaction Object to the bank, how will bank know what is the type of transaction and how will it get the details to perform transaction? I would like to know how can you access the other child specific details from the transaction object? Will you typecast transaction to the Specific object?
@meme_engineering45212 жыл бұрын
bhai ye kya seedha code kara diya, class diagram nahi banaaya wth