Hi, in this video we have covered #strategy #designPattern out of many design pattern which is asked in Low level system design interview. ➡️ Become a Member: / @conceptandcoding
I don't know if anyone else is able to appreciate it, but man the idea of interface and this design pattern is absolute genius. Another day when I'm surprised what all things humans have achieved
Thank you for this tutorial. Just to add, The fundamental of every design pattern is to separate out what changes over period of time from what remains constant. As you see in Strategy pattern, we are trying to separate out dependency of drive from the main class as much as possible by making various strategies to inject it dynamically based on client requirement so that in future if new requirement for drive comes, there will be minimal/no changes in existing code(Open closed Principle).
Favour composition over inheritance. Separate what stays the same from what changes. As we are using a new operator, it's a program to an implementation not to an interface. We can use the factory pattern here. Right?
@@niwanshumaheshwari4534 using new operator doesn't mean we are programming to an implementation ; it's about how you're using it in relation to abstraction and interfaces. correct me if I'm wrong.
@@niwanshumaheshwari4534 Also you client should be the one who should initialize the class. You can inject your classes using types in static type languages and using type hints in python
litreally , amazing content , from monday there will be my interviews , if i will get selected than i will defenatly return to this video and comment over this .......amazing one
Legit content! Probably one of the best and simplest explanations of a Design Pattern. I was literally stuck on an LLD of a Netflix like subscription service, this video helped me find the solution. Guess what? It's Strategy Pattern!
I got rejected in an interview because of the lack of knowledge of design pattern. Going to learn from you next time will make a stronger comeback . 💥💥
You are correct. My interview got scheduled for 3 hrs(F2F) but got finished in 15mins. I felt very bad at that moment. Many times I tried but was not able to catch concepts of design patterns. I always use to think in C with classes. Your Design pattern tutorial is helping me a lot to understand. Converting your code from java to C++ to and understanding the concepts of design patterns. Started learning now. Thanks for explanations.
It took me more than an hour to understand this while going through the Head First Book for the same design principle. Should have gone through the video first. Now I am going to use this "strategy", in which I will refer to your video first and then will go through the book
I have finally started going through your , LLD Playlist, and I will comment something on every video after watching. Not always need to be Praise or Learnings from the video.
In laymen terms, In Startegy Design pattern we create an interface and it's different implementation based on strategy !! And inject appropriate startegy in client class by creating constructor or any injection of your choice
it's really frustrating because I just know this would be good but only speak English. tried captions and translate but too confusing. and chance to redub some of these ? great tutorials
If you are looking for C++ code : using namespace std; #include #include using namespace std; class drivestratergy{ public: virtual void drive()=0; }; class normalDrive : public drivestratergy{ public: void drive(){ cout
Hey bro , you have an awesome knowledge and course agenda , it would have been better if you've xplained it in English instead in hindi. It's very hard to understand and concentrate🙂🥲. Appreciate your efforts
1) Using a Drive Interface with Concrete Implementations 2) Using a Single Drive Class with Behavior Specified in the Constructor Which is better approach
Hi Shreyansh, Your videos are awesome. But I would like to know the below things 1. which one we should start first hld or lld? 2. In what way we should learn hld and lld? 3. How to practice these and gain hands on experiene? 4. Is it necessary to take a course after watching your videos? 5. Any order, you would reccomment to follow? Please clear my doubts Shreyansh.
You should always go ahead with the LLD first, even some companies don't have this round explicitly but then it assumed you should know these principles already. Then you go HLD. For both of them see videos on a lot of problem use cases. You will be able to grasp these concepts well
wonderful explanation dear. Just one suggestion(pls correct me if I am wrong), I think we have to give different name like myDrive() instead of drive() in Vehicle class. It will implicitly differentiate method used inside DriverStartegy.
I have a few queries, maybe it will sound childish but I will ask anyway. We know there are 3 types of design patterns. Creational, structural and behavioral. i) Do we need to use all of these three patterns to make a full end to end application? i) If not then Can a single type of pattern handle all of the basic scenarios (creation, responsibility assignment to object etc. iii) is there any pattern which helps more during the interview.
Hi Rahman, very good question. Let me try to elaborate: - Do we need to use all 3 types of patterns to make an end to end application. Answer is NO. Using Design pattern is not mandatory. You can build system without using any pattern and live with it if system is Readable, Scalable, Manageable etc. You dont need design pattern. Let say for solving one part of the system you need to use some pattern, you can use a pattern from any type not necessary to use pattern from all 3 types. - Single pattern for helping in Interview, thats a tough question, i would say that depend on what question you get in the interview, basics questions can be created through common design patterns like Factory,Structural. But for some specific questions like design logging system, design Notify system we need to know those patterns in advance or come up some clean design during interview itself.
@@ConceptandCoding thank you for clearing the doubts. So basically during the interview for any particular scenario, I need to start with a design pattern which will suit most with the basic requirements. And need to add any additional design pattern for any new type of requirements. Eg: If asked to create a parking lot system, and if the basic requirements are can have multiple types of cars Can have multiple floor Can have multiple entry exit I can start with something like an abstract factory or factory pattern. If by any chance we need to log these events, we can use singleton pattern. Correct me if I am wrong. Thank you once again for prompt reply.
Sir From my knowledge we cant create objects of interface. But what I am able to analyse from above example is that we can create a has-a relationship using object of interface but we have to define the functions of interface in the class where object is declare?......Do let me know whether I am correct or not? BTW you are creating some GOD level content❤ Please don't stop, I am ready to help you in every possible way.
let me check the video Hardik and then i will be able to clarify your doubts. But one thing i can tell is this is design pattern video, so pattern defined in this, and class and their relationship will be correct as its well documented.
One concern, Please take a look the arrows in UML diagram while showing parent child relationship arrows are pointing to parent instead of child. I have verified that those should point to child could you please comment on that. Because earlier it was confusing for me..
Brother, Normal Drive Strategy class would implement Drive Strategy that means it has-a relationship but in diagram it is-a relationship. Implements are always has-a and extends are is-a. Am i right or missing something?
I am aware of the basics of design pattern and some common principle such (as SOLID, KISS, DRY, etc) as they come into use in writing better code in general but I want to know from an interview perspective how deep one need to go say in my case I have an experience of 1.2 years and going for an interview how low do I need to go and design when it comes to LLD, I was always skeptical about LLD to what extend can we go low, in short, does experience affects the quality of solution or is it just like DSA questions same for everyone. P.S I haven't experienced any such LLD questions so far so if you can clear things here would be really helpful And sorry long explanation 😅
Hi Danish, i can definitely tell you are good in coding and DSA. And regarding LLD, there is no Level (which you can go deep). Level might be there in HLD where you can go deeper n deeper on one part of the design, like DB design, next level is RDBMS or No SQL then next level is Master slave then next level is Partitioning then sharding etc. But for LLD, its all about how good is your understanding with Objects, from the given problem are you able to identify Actors (objects), then what all features(member variables) it should have and then function. And how these different object interact with each others / what would be their relationship. Thats what Design pattern will help and to identify when and where which design pattern need to apply, that comes with experience or practice. Sorry for the long answer 🙂
@@ConceptandCoding Hey Thanks for those kind words, I hear you and it totally make sense specially "identify Actors" and finally relationship , will take those input and start learning/practicing accordingly 🙏
Can someOne tell me the arrow Notation between DriveStrategy interface and normal drive , special drive is correct ? As DriveStrategy is interface and normal drive is class so the relationship between them should be has a relationship and arrow should be like -------> . See at 7:25.
i have remake all patterns in english too, pls check “All creational design patterns”, “All structural design patterns” and “All behavioral design patterns” in 1 video in the LLd playlist itself
Note for my future reference 5:51 -> at the same level children are using same code , code is not reusable solution -> make the common part as interface type
Good video for strategy design pattern, can you please make a video where you solve a complete lld problem and show usage of strategy design pattern in the solution. If there is any solution you created in lld design that has usage of strategy design please let me know.
Why don't we create Vehicle as an interface and then create 2 more interfaces SprecialCapabilitiesVehicle and NormalCapabilitiesVehicle which extends Vehicle and has default implementation for drive respectively? Now the PassengerCar implements NormalCapabilitiesVehicle and SportsCar and PassengerCar implements SpecialCapabilitiesVehicle.
this is because, lets assume, later on another functionality like display() will be added and it would be same for sport cars and passenger car and not in off road car, then we can create similar strategy for display and inject them in vehicle constructor. Adding more interfaces will not be a good scalable option with increase in features.
As you update and add new features, how many interfaces you will add and how many interfaces you will refactor? That is the reason we should not opt for this.
We are using strategic design pattern to share common logic in subclass. Why can't we create a util function instead of following strategic design pattern?
Why can we not assign NormalDriveStrategy in the Vehicle class, any how if super constructor is called from child class it will be over writing with the drive strategy provided by the child class. This will be useful to have default drive strategy defined. Suggest issue with this approach ?
isnt arrow you mentioned in starting for has a belongs to single direction association in uml diagrams. Am I missing something. Great content tho, learned a lot. Thanks
Hi Akshay, to make the UML and LLD easy to understand, i used these arrows for explaining is-a and has-a relationship. And in interview, at-least i haven't faced any issue bcoz of this arrows. But once you get the understanding better of classes, objects and relationship, then you can learn all UML arrows (which i found very hard to remember)
No, for everyone function we can not create a new class. Else we will create another problem called class explosion. We can keep related functions in one class.
