The best playlist on Design Patterns I have seen so far. Your way of explanation, examples, animations everything is top notch. Thanks a million to you.
I presented similar design in one of the tech interviews and was questioned on breaking OCP in factory class. Though this is mostly taught by most authors for explaining the concept, in reality, we can avoid switch case with map so factory method just look up the map and return the value. Now to build the map, we have two choices 1. Provide register product method in factory so product can register itself and then can be returned 2. Use reflection to load classes in a map at startup. Map is maintained by factory class. Map key is identifier used in switch case and value is return type of factory method.
Both ways are good enough as an alternate to switch case. At the end factory does have knowledge of the map or the way to figure out the concrete class.
@@sudocode if you agree, would you consider editing the video or add a top level comment to let readers know about this. It might save them from getting kicked out from their dream jobs at no fault of theirs.
9:51 CreateCourse() is not the meat and potatoes of the Factory pattern. The Factory pattern relies on delegating the object creation to a class specialized for this purpose. The underlying mechanisms of the actual creation vary by use case and are beyond the scope of the Factory pattern.
1. 2:28 the class that implements the creation logic is wrongfully called "concrete" class, or subclass, that implement the factory method interface. The "factory" class need not be an abstraction for the creation implemention but a totally separated class. This is because you want to decouple the objects being created, from the factory (see 5.). 2. 2:56 the same thing. You say that the FactoryClass is abstract or an interface. 3. 4:40 the concrete class is _not_ hidden from the interface that it implements, it just can't be. But it is hidden from the client. 4. 9:51 In the Course example you make the Course class abstract. Furthermore you have an abstract method named createCourse() which would suggest it's responsible for the underlying logic of a factory method like newing the Course. In fact it has to do with inner composition of a Course but not with its instantiation. 5. You made the CourseFactory not an abstract class/interface and well you did. But remember what you said in 1. and 2. But you name the instantiating code getCourse() which would suggest it returns a permanent unique field of the class. You should name _this_ createCourse() or just create().
Before coming to this tutorial, I am having, doubts about design pattern but the way explained all the things it is easy to understand. Thank you very much for such informative video ☺
Bahut kam log samjha pate hai is tarah ! Aap unme se ek hai. Thanks for this explaination, I was wondering why this series is not resumed , Hoping you will continue and we will get best out of this series !
Hi Yogita Maam , At 4:15 you showed in diagram that Factory Class contains no implementation .That is not the case as in factory class,factory method should contain the logic to determine one of the concrete class.In the slide you showed , logic to detremine which subclass is resposibility of subclass but thats not the case as logic to determine which concrete class is the responsibility of Factory class . Could you please clarify on this ? package com.journaldev.design.factory; import com.journaldev.design.model.Computer; import com.journaldev.design.model.PC; import com.journaldev.design.model.Server; public class ComputerFactory { public static Computer getComputer(String type, String ram, String hdd, String cpu){ if("PC".equalsIgnoreCase(type)) return new PC(ram, hdd, cpu); else if("Server".equalsIgnoreCase(type)) return new Server(ram, hdd, cpu);
@@sudocode Yes .But thta's not correct.Initialization to create actual object is always done in factory class.see below code 2 code from geekfor fees and journaldev . public class NotificationFactory { public static Notification createNotification(String channel) { if (channel == null || channel.isEmpty()) return null; switch (channel) { case "SMS": return new SMSNotification(); case "EMAIL": return new EmailNotification(); case "PUSH": return new PushNotification(); default: throw new IllegalArgumentException("Unknown channel "+channel); } } } public class ComputerFactory { public static Computer getComputer(String type, String ram, String hdd, String cpu){ if("PC".equalsIgnoreCase(type)) return new PC(ram, hdd, cpu); else if("Server".equalsIgnoreCase(type)) return new Server(ram, hdd, cpu);
I agree with Saumitra Saxena. In your example also CourseFactory has logic to initialize object of concrete class like HLD, LLD and not the concrete class has that switch case logic. This is done to ensure only Factory class is open for changes and rest are closed for modifications.
Hello and geetings from Bulgaria. I like your energetic and well explained courses. However ... I can see for last ... many years that it is the Indian scholars pushing the abstract methods while many other have given them up. For ex. the whole C# platform is based on the implementation of interfaces. Which in OOP terms gives us the "is a" relationships. Down the line that also help to implement the very modern now concepts like dependency injection and automatic unit tests. In both cases we can inject an object as another object's "has a", as well as we can inject a Mock object with pre-setup return values. That is for as long as those objects implement the desired interfaces. I would love to engage you on small chat / discussion about that. Thank you, ILIIA
Thank you for your comments. I would have loved to chat with you if you haven’t opened with the Indian scholars. Computer science is a science. It has nothing to do with origin of the scientists. Wish you well 😊
@@sudocode Word scholars is a valid word and it has a meaning within any science regardless how precise science is. If one looks for insult he or she will inevitably find it. Wish you well
Hello. I appreciate your effort. I have a question regarding the switch statement in your CourseFactory class as well as else-if statements in the vehicles example. Aren't those breaking the open-closed principle?
No they are not. They are open for extension in a sense you can add more courses but they are closed because each course has its own createCourse method which you cannot modify :)
I think we cannot strictly follow each of the principles. They are subjective and we need to think based on what is easier and feasible for the given scenario.
If i create multiple concreate class based on vehicle type (TruckCreator, CarCreator, PlaneCreator) than based on type of vehicle if i return the creator class then that factory interface isnt working like facade class? please answer
Hi Yogita, can you please upload the code online and share the code url in the description. So that we can also try manipulating the code for the given design pattern.
As always on to the point and easy to understand . waiting for another design pattern video. I have one off the topic query . how is your experience on LinkedIn Learning? dose it actually add some extra point when it comes to big companies ?I would really appreciate your response. Thanks !
𝗦𝗶𝗺𝗽𝗹𝗲 𝗙𝗮𝗰𝘁𝗼𝗿𝘆: A class with a single method that creates objects of different types based on provided input. Not a "true" Design Pattern: Often considered an implementation technique rather than a formal design pattern. 𝗙𝗮𝗰𝘁𝗼𝗿𝘆 𝗣𝗮𝘁𝘁𝗲𝗿𝗻 (𝗔𝗯𝘀𝘁𝗿𝗮𝗰𝘁 𝗙𝗮𝗰𝘁𝗼𝗿𝘆): A design pattern that provides an interface for creating families of related or dependent objects without specifying their concrete classes. Delegates the responsibility of instantiation to a subclass or an interface, adhering to the Open-Closed Principle (OCP).
just search a good programming language that is in demand and has a future. Apart from programming there is a lot career choice in IT, Qa( software testing) , network security , DBA etc
The best playlist on Design Patterns I have seen so far. Your way of explanation, examples, animations everything is top notch. Thanks a million to you.
I presented similar design in one of the tech interviews and was questioned on breaking OCP in factory class.
Though this is mostly taught by most authors for explaining the concept, in reality, we can avoid switch case with map so factory method just look up the map and return the value. Now to build the map, we have two choices
1. Provide register product method in factory so product can register itself and then can be returned
2. Use reflection to load classes in a map at startup. Map is maintained by factory class. Map key is identifier used in switch case and value is return type of factory method.
Both ways are good enough as an alternate to switch case. At the end factory does have knowledge of the map or the way to figure out the concrete class.
@@sudocode if you agree, would you consider editing the video or add a top level comment to let readers know about this. It might save them from getting kicked out from their dream jobs at no fault of theirs.
Any sample code for for not vloilating OCP, please share.
We use map in our project
I was about to say OCP....You pointed out
9:51 CreateCourse() is not the meat and potatoes of the Factory pattern. The Factory pattern relies on delegating the object creation to a class specialized for this purpose. The underlying mechanisms of the actual creation vary by use case and are beyond the scope of the Factory pattern.
The second example was little bit complicated but I really like createVehicle example. Thank you for explaining in easy manner.
Do you mean the factory example was complicated or the coding example ?
@@sudocode the course module example. I am at intermediate level may be it’s easy to understand for someone who knows better than me
1. 2:28 the class that implements the creation logic is wrongfully called "concrete" class, or subclass, that implement the factory method interface. The "factory" class need not be an abstraction for the creation implemention but a totally separated class. This is because you want to decouple the objects being created, from the factory (see 5.).
2. 2:56 the same thing. You say that the FactoryClass is abstract or an interface.
3. 4:40 the concrete class is _not_ hidden from the interface that it implements, it just can't be. But it is hidden from the client.
4. 9:51 In the Course example you make the Course class abstract. Furthermore you have an abstract method named createCourse() which would suggest it's responsible for the underlying logic of a factory method like newing the Course. In fact it has to do with inner composition of a Course but not with its instantiation.
5. You made the CourseFactory not an abstract class/interface and well you did. But remember what you said in 1. and 2. But you name the instantiating code getCourse() which would suggest it returns a permanent unique field of the class. You should name _this_ createCourse() or just create().
Before coming to this tutorial, I am having, doubts about design pattern but the way explained all the things it is easy to understand.
Thank you very much for such informative video ☺
Very well explained, have been searching for the videos and got this. You saved my life. Thank you ❤
Great example. If you can also explain the code flow through debugger, that will help to understand code much better.
This is an amazing video. Thank you for the wonderful explanation. First time I understood what Factory method pattern is actually meant for.
You are amazing! Thanks for creating HLD, LLD, and Design patterns courses.
Bahut kam log samjha pate hai is tarah ! Aap unme se ek hai. Thanks for this explaination, I was wondering why this series is not resumed , Hoping you will continue and we will get best out of this series !
Thanks. Check the community posts and you will know why the delays in series 😊
@@sudocode Pakka
I really love your video editing work 😍
Excellent explanation. Could you please add video for decorator design pattern?
Crystal Clear Explanation. Thanks!
Nmrl parça, finalmente consegui entender o bgl, tmj
Supreb expiation ❤️👌👌
You always made easy 😊
What is the program you use to create class diagrams???
does it corelate to open / close principle. if one of the new requirement there will be modification , any alternative for this ?
Useful information, but maam dnt you think swich is violating OCP in case we have to add new type.. If not then can you please explain??
Use map instead of switch here, load this map from properties file on startup
Great video, yogita.
btw, do you have someone for your video editing or how do you do it?
Hi Arpita, can you please take more use cases for Low-level design eg. Parking lot, School Management Systems, Hospital Management System, etc?
In which of the scenarios would you use factory pattern and why?
Consuming a service
Complex Validation
Logging
Data Binding
None of the Above
Where can we find the code that was explained in the video ?
Hi Yogita Maam , At 4:15 you showed in diagram that Factory Class contains no implementation .That is not the case as in factory class,factory method should contain the logic to determine one of the concrete class.In the slide you showed , logic to detremine which subclass is resposibility of subclass but thats not the case as logic to determine which concrete class is the responsibility of Factory class . Could you please clarify on this ?
package com.journaldev.design.factory;
import com.journaldev.design.model.Computer;
import com.journaldev.design.model.PC;
import com.journaldev.design.model.Server;
public class ComputerFactory {
public static Computer getComputer(String type, String ram, String hdd, String cpu){
if("PC".equalsIgnoreCase(type)) return new PC(ram, hdd, cpu);
else if("Server".equalsIgnoreCase(type)) return new Server(ram, hdd, cpu);
return null;
}
}
It means no implementation to initialise the actual object creation :)
@@sudocode Yes .But thta's not correct.Initialization to create actual object is always done in factory class.see below code 2 code from geekfor fees and journaldev .
public class NotificationFactory {
public static Notification createNotification(String channel)
{
if (channel == null || channel.isEmpty())
return null;
switch (channel) {
case "SMS":
return new SMSNotification();
case "EMAIL":
return new EmailNotification();
case "PUSH":
return new PushNotification();
default:
throw new IllegalArgumentException("Unknown channel "+channel);
}
}
}
public class ComputerFactory {
public static Computer getComputer(String type, String ram, String hdd, String cpu){
if("PC".equalsIgnoreCase(type)) return new PC(ram, hdd, cpu);
else if("Server".equalsIgnoreCase(type)) return new Server(ram, hdd, cpu);
return null;
}
}
I agree with Saumitra Saxena. In your example also CourseFactory has logic to initialize object of concrete class like HLD, LLD and not the concrete class has that switch case logic. This is done to ensure only Factory class is open for changes and rest are closed for modifications.
The Content is impressive, presentations. Which software used to create this content?
Thank you for the video on an import pattern 👍
Hello and geetings from Bulgaria.
I like your energetic and well explained courses. However ...
I can see for last ... many years that it is the Indian scholars pushing the abstract methods while many other have given them up. For ex. the whole C# platform is based on the implementation of interfaces. Which in OOP terms gives us the "is a" relationships. Down the line that also help to implement the very modern now concepts like dependency injection and automatic unit tests. In both cases we can inject an object as another object's "has a", as well as we can inject a Mock object with pre-setup return values. That is for as long as those objects implement the desired interfaces.
I would love to engage you on small chat / discussion about that.
Thank you,
ILIIA
Thank you for your comments. I would have loved to chat with you if you haven’t opened with the Indian scholars. Computer science is a science. It has nothing to do with origin of the scientists. Wish you well 😊
@@sudocode Word scholars is a valid word and it has a meaning within any science regardless how precise science is.
If one looks for insult he or she will inevitably find it.
Wish you well
Hello. I appreciate your effort. I have a question regarding the switch statement in your CourseFactory class as well as else-if statements in the vehicles example. Aren't those breaking the open-closed principle?
No they are not. They are open for extension in a sense you can add more courses but they are closed because each course has its own createCourse method which you cannot modify :)
@@sudocode what if I want to extend your app by creating another type of course? Will I have to modify your class?
I think we cannot strictly follow each of the principles. They are subjective and we need to think based on what is easier and feasible for the given scenario.
Wait ! Whats that VS Code extension for generating class diagram
This is simple factory. The factory method pattern by GOF will have subclasses create the instances
If i create multiple concreate class based on vehicle type (TruckCreator, CarCreator, PlaneCreator) than based on type of vehicle if i return the creator class then that factory interface isnt working like facade class? please answer
Excellent 👌👍
Can we have example of strategy DP too?
where can i get the slides or animation doc used in the course??
Hello mam, it looks like you're using premium features of IntelliJ , is it provided by your company or you bought the license on your own ?
I have my own license
Hi Yogita, can you please upload the code online and share the code url in the description. So that we can also try manipulating the code for the given design pattern.
Nice explained
Doubt:-
Is it the same method that's used to expose transaction API's of any bank to Amazon kind of 3rd party
what about abstract factory pattern?
Q: What if LLD and HLD class would have different constructor dependencies?
After long time
thanks for such video
You have not used createCourse method in factory method to create instance instead used new Class() directly.
As always on to the point and easy to understand . waiting for another design pattern video.
I have one off the topic query . how is your experience on LinkedIn Learning? dose it actually add some extra point when it comes to big companies ?I would really appreciate your response. Thanks !
This is simple factory only. Not a factory pattern.
Yes. I was looking for this comment.
𝗦𝗶𝗺𝗽𝗹𝗲 𝗙𝗮𝗰𝘁𝗼𝗿𝘆: A class with a single method that creates objects of different types based on provided input.
Not a "true" Design Pattern: Often considered an implementation technique rather than a formal design pattern.
𝗙𝗮𝗰𝘁𝗼𝗿𝘆 𝗣𝗮𝘁𝘁𝗲𝗿𝗻 (𝗔𝗯𝘀𝘁𝗿𝗮𝗰𝘁 𝗙𝗮𝗰𝘁𝗼𝗿𝘆): A design pattern that provides an interface for creating families of related or dependent objects without specifying their concrete classes.
Delegates the responsibility of instantiation to a subclass or an interface, adhering to the Open-Closed Principle (OCP).
Where can I find the code?
Can I get the source code please?
👏👏👏👏👏
I am bca first year student . Can i become a software engineer? Plz tell me roadmap.
ofcourse
just search a good programming language that is in demand and has a future.
Apart from programming there is a lot career choice in IT, Qa( software testing) , network security , DBA etc
Why have you stopped making videos. You don't how popular are your videos amongst students
I will be making more. Just took a short break.
KINDLY SHARE THIS FACTORY METHOD PACKAGE THAT U HAVE IMPLEMENTED
complete the playlist quickly
i think that code is completly wrong
theory was right but the implementation was very poor
❤