Loved the way you explained the concept by taking an example and Step by step writing the code, talking about its disadvantages, and then coming to a solution by demonstrating the importance of Factory Method. Waiting for your upcoming videos.
There are plenty of resources for Design patterns in java and python on the internet but very few good resources for C++. This Design pattern series is like an oasis in desert for C++ developers. Thank you so much Keerti.
At 4:25 we see that in our directory we have 6 files, bike.hpp/cpp; car.hpp/cpp; vehicle.hpp/cpp.But upon following the lecture from 1:35 till 4:25 we see that "vehicle.cpp" was never created, we only worked with "vehicle.hpp" throughout the mentioned time-range.What's inside "vehicle.cpp" ? then.Also At 5:10 while creating the library archive "vehicle_library.a", "vehicle.o" was not put into it just like "car.o" and "bike.o" were put. Was it intentional or a miss ? Same happened from 13:55 onwards while creating a library for "smart_client" i.e we didn't put "vehicle.o" into our library.Please shed some light on these points.
If the object files are not added to the library, just exclude them from the compilation. Since the correct header files are used in car and bike cpp files, it should not be a problem.
A great series to start really since there is so less quality content available on design patterns. Looking forward for next videos! One feedback, I feel many of the beginners must be struggling with the C++ commands to create excutable cpp files and archives or libraries. A brief explanation on those commands in the beginning of the next video or a separate video would really help.
You have to provide the pre requites to start this series. These things might not be known to everyone, considering myself to be an average student who has studied OOPs in C++. 1. Code in header file. (How to write like #ifndef, etc). 2. Less clarity of how many files already created and why? 3. Everything was overwhelming. Should be slow and creation of files should be shown so that one can follow along. 4. commands needs to be explained of the terminal. Idk about the rest but these are my honest opinions.
But isn't it still breaking the OpenClose Principle of Design Pattern. because we still need to make change in factory code whenever new vehicle is added!!!
Used it in an Web Application where the application had to handle multiple database or different types. I needed to create the database object depending on the connection string passed.
I've used Factory design pattern once. I was wondering why we move the same if else logic into another class. Isn't it same.. But now it makes complete sense. We need to abstract the logic from the client code. Thanks !
@@KeertiPurswani Sure, I liked that it does not have any complicated code examples. The intention was just to understand what problem it overcomes and makes our life easier as a developer. And yeah, rest of the tutorials can be like this !
Hi Kriti , I'm learning design patterns for the first time and I found some challenges in your video like you directly moved into the practical implementation and had not tell that for what purpose it is used for..... So I have to go somewhere else to understand that then I come back to your video. So please look into this issue. While the remaining explaination is really good. Thanks
Thank you so much. I have been searching for many tutorials to know about design patterns in c++. I’m lucky that I came across this Vedio. Your explanation is simply superb
Just waao Di, got it very easily, i have been reading the online vlogs and tutorials and always i was getting confused and not clear to me....., but this video made everything super easy ♥️💯 One request, please complete this Playlist as soon as possible please 🙏 💜
This was an amazing lecture. Superbly explained, all doubts cleared. Please ma'am explain all the possible design patterns. Really looking forward to this series. 👍
@@KeertiPurswani Sure ma'am. Shared the video with all my friends and now you've got a bunch of folks ready to be taught design patterns using C++. Keep up the good work.👍😊
With this if else you are polluting the Factory class as well. Imagine adding 10 more type of vehicles tomorrow. You have to maintain a registry of vehicle types added in a kind of hashmap. The key being the vehicle type, the value is the vehicle object.
Nice explanation.. the way you explained the concepts of factory pattern is different than others (through library creation)..hoping for more videos.. for remaining patterns advantages and drawback of using that pattern can also be discussed
I can tell you where Recently I have used this Pattern: I have designed three classes: 1. GkeAgent 2. EksAgent 3. AksAgent Interface: IKubernetesService Implemeted Factory KubernetesServiceFactory. Based on the Properlty file value of the cloud type i am returning the suitable object.
I'm familiar with some design patterns like this, and hence, could follow everything properly. But thinking from a beginner's perspective, it could have been better :) Few observations: 1. The explanation was tightly coupled to C++. A person learning design patterns shouldn't have to start with the library creation approach, that too involving C++ commands. Those are extra details that can be picked up later, if needed. I feel like you could have gone with a more generic and simpler approach, especially since this is the "Simple Factory Pattern". 2. The video was kinda short. An in-depth explanation spanning half an hour would have been better. For instance, a comprehensive explanation could have been provided regarding the object creation approach, i.e., the reason behind doing Base B = new Child() instead of Child C = new Child() and its impacts since this acts as a prerequisite to understanding the factory approach.
I have one doubt of this kind of implementation of factory design pattern , I.e this code violate the open and closed principle of SOLID . Because whenever you will be adding new condition in the factory method you will be modifying , but principle says you code should be open for extension and closed for modification. So how could you handle please explain.
@keerti can you please create videos explaining all design patterns as i don't find many design patterns easy to learn and adapt content. btw great job, you nailed the content on your channel. I am software engineer and currently pursuing masters from ASU and preparing for interviews for SDE2 roles.
@keerti thank you for responding back and today I hold SD3 offer from Oracle and have started job previous week. Thank you for motivating and influencing Relevant content. Much love 😍
The bike and car are stored in a vehicle reference. What if there are functions which are not present in vehicle class but are present in bike or car class (not talking about overridden functions)?
Hi Keerti, the client was still required to call createVehicle which i think could have been handled by the factory itself unless createVehicle is parameterised. Can you please explain why there is distinction between default constructor and createVehicle and what createVehicle is supposed to do?
Please make a detailed video on how to make linkedin profile so strong that recruiters of tech giant's approach freshers (2020passouts) for job openings.
i really like the way you explained. The example was not at all complex, simple vehicle objects work like charm. Would love to see a dedicated Design Pattern series which could help someone prep for OOD. Great Content.
thanks for this video. but.. whenever we make any changes in our factory class (say we add bus class), then we do need to recompile the whole factory class, as well as ask client to update the factory jar which they are using.. so is there any way to overcome this as well in this design pattern ??
Hey Keerti, I just watched the video and I was able to get the concepts and advantages that you talked about in the video but I struggled with the implementation part cuz most of the things were completely new for me. So, could you please suggest any resources for learning the implementation of libraries and header files in c++?
Thanks mam until I worked on cpp 98 version.now I started giving interviews.i faced questions on design patterns I don't how they work,how I want use in project ur videos help lot to understand concept and practical Thank u mam a lot please do videos mam
Hi Keerti, Great explanation. I see some of createFactory classes include around 7-10 constructor arguments and pass the exact same or 1-2 more arguments to create the underlined class. It is little tightly coupled because does not give flexibility to accept new type of class in factory method, is this correct approach? To refactor, I think I can use ClassName as parameter in createFactory, and there will be additional 7-10 constructor arguments passed along.
Hi keerti, I seen this factory design pattern video in that you create factory for separation of vehicle type. We can do that in stored procedure pass car, bike,truck, bus and get only those record and get faster execution can you give one more real time example
in first place you have not included vehicle oblect file vehicle.o in the vehicle liberary, you only added car & bike object file to library. Please explain
I believe in the last code example the vehicle objects are actually getting created in the factory method getVehicle method. The name of the funtion in bike and car classes should be changed from create vehicle to something else.
I know I am super late but never stopped, had a lot going on in personal life. Uploaded the new video today and hoping to finish the series super soon. Hope you like the video!
Hi Keerthi, rather than going with the bookish / standard definition you have explained in in simple terms so that even novice programmer can understand. but I have a query here , you said that whenever there is a change in the requirement from the client we need to change the library and give it back to the client, I mean when client needs TEMPO vechile, we need to change the library and give it to him right ??
For your upcoming video please zoom into your code so that we can get a clear view of it .... Lots of love ❤️❤️ love your teaching and love your contents
U really made whole concept soo easy..thanks alot. One request is it possible to make video on abstract factory. It seems bit difficult for me to understand conceptually. I understand when they give some example but still not able to understand when and where to use
Thank you very much for all your C++vedios. The videos are of great value. But, I still have question on factory design pattern. With the VehicleFactory class introduced , we are making smartclient independent as the code for any new vehicle needs to be implemented in VehicleFactory. However, dependent library for smart client is changing and that needs to be delivered to client everytime a change is made right........ Where as without vehicleFactory client.exe should be rebuild by changing all the dependent libraries. My question is in anycase client gets a new deliverable right....
Awesome simplified explanation Keerti! 🙂Please continue the series covering major design patterns using c++ code examples. Please give a thought about making a video series on C++ multithreading as well. Many thanks! Keep up the good work. 🙂
It was Really a good one to start with Design Patterns. Really Looking forward to this series. It would be even more good if you add descriptive things to remember at the middle or end to make a note of it for future reference and also adding interview perspective to this. Thanks Keerti.
This is The Simple Factory pattern, not The Factory Design pattern. "The Simple Factory isn’t actually a Design Pattern; it’s more of a programming idiom." according to Head First Design Patterns. In addition, the use cases for the Simple Factory and Factory methods are not the same. The Factory method uses inheritance to provide a common framework; it does more than merely create objects.
Really great content. I will just request you to release other lectures soon, so that the continuity doesn't breaks. Thank you for sharing your knowledge..
Few points needs to make clear. 1. Why that factory class is made static if not then what would happen? In real world scenrio is it done like this? 2. More examples related to real work. The content length is good. Keep that but make it more advanced with focusing on low level design. 👍
The factory class is _not_ static - that was clarified several times in the video. Only the getVehicle() method is static. If it was not, you would have to create an instance of the factory before you could use the getVehicle() method.
But mam apko still jo first command hai gcc and all class name if age chal k truck ka class aya to usko bhi aapko gcc me lena hi padega so cpp me is that a problem or not I am not sure but This design pattern definitely solves problem of object creations for above use case
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
Loved the way you explained the concept by taking an example and Step by step writing the code, talking about its disadvantages, and then coming to a solution by demonstrating the importance of Factory Method.
Waiting for your upcoming videos.
ua-cam.com/play/PLuO_Xyt86T60SIBUCHCEof_1ggJWH6QsQ.html
There are plenty of resources for Design patterns in java and python on the internet but very few good resources for C++. This Design pattern series is like an oasis in desert for C++ developers. Thank you so much Keerti.
I'm a c++ developer and was struggling to know the concept, believe me this is the best explanation I could find on UA-cam. Thanks for the video
Thank you so much! Means a lot! ❤️
At 4:25 we see that in our directory we have 6 files, bike.hpp/cpp; car.hpp/cpp; vehicle.hpp/cpp.But upon following the lecture from 1:35 till 4:25 we see that "vehicle.cpp" was never created, we only worked with "vehicle.hpp" throughout the mentioned time-range.What's inside "vehicle.cpp" ? then.Also At 5:10 while creating the library archive "vehicle_library.a", "vehicle.o" was not put into it just like "car.o" and "bike.o" were put. Was it intentional or a miss ? Same happened from 13:55 onwards while creating a library for "smart_client" i.e we didn't put "vehicle.o" into our library.Please shed some light on these points.
same doubt
If the object files are not added to the library, just exclude them from the compilation. Since the correct header files are used in car and bike cpp files, it should not be a problem.
I use this in most of my projects. I didn't know it was called factory method.
Thank you for teaching.
A great series to start really since there is so less quality content available on design patterns. Looking forward for next videos!
One feedback, I feel many of the beginners must be struggling with the C++ commands to create excutable cpp files and archives or libraries. A brief explanation on those commands in the beginning of the next video or a separate video would really help.
Yes this is highly required as all the commands here are going above my head.
Start of much needed series. My interviews are coming up so I don't know how much it will benefit me but this is a great start.
You have to provide the pre requites to start this series.
These things might not be known to everyone, considering myself to be an average student who has studied OOPs in C++.
1. Code in header file. (How to write like #ifndef, etc).
2. Less clarity of how many files already created and why?
3. Everything was overwhelming. Should be slow and creation of files should be shown so that one can follow along.
4. commands needs to be explained of the terminal.
Idk about the rest but these are my honest opinions.
Go first learn and practice OOPs again. All the things were really basics of OOPs
I agree, I think C++ knowledge is pre-requisite here, it'd have been better if this was explained in Python
Serious ly u have explained the concepts very clear.. till date I was using all this in my code without knowing why.. superb..
But isn't it still breaking the OpenClose Principle of Design Pattern. because we still need to make change in factory code whenever new vehicle is added!!!
Used it in an Web Application where the application had to handle multiple database or different types. I needed to create the database object depending on the connection string passed.
Great explanation. Thanks a lot for doing this design pattern series !!
I've used Factory design pattern once. I was wondering why we move the same if else logic into another class. Isn't it same.. But now it makes complete sense. We need to abstract the logic from the client code. Thanks !
Yaaaaay!! Thank you! 😇😇
Any constructive feedback? Rest of the tutorials should be like this only?
@@KeertiPurswani Sure, I liked that it does not have any complicated code examples. The intention was just to understand what problem it overcomes and makes our life easier as a developer.
And yeah, rest of the tutorials can be like this !
Hi Kriti ,
I'm learning design patterns for the first time and I found some challenges in your video like you directly moved into the practical implementation and had not tell that for what purpose it is used for..... So I have to go somewhere else to understand that then I come back to your video. So please look into this issue.
While the remaining explaination is really good.
Thanks
Thank you so much. I have been searching for many tutorials to know about design patterns in c++. I’m lucky that I came across this Vedio. Your explanation is simply superb
Just waao Di, got it very easily, i have been reading the online vlogs and tutorials and always i was getting confused and not clear to me....., but this video made everything super easy ♥️💯
One request, please complete this Playlist as soon as possible please 🙏 💜
I am sorry for being so late but I hope the quality pf explanation will make it upto you. Hoping you like the new videos! ❤️
This was an amazing lecture. Superbly explained, all doubts cleared. Please ma'am explain all the possible design patterns. Really looking forward to this series. 👍
Thank you so much Saurav, means a lot! Please do share the videos with your friends 😇😇
@@KeertiPurswani Sure ma'am. Shared the video with all my friends and now you've got a bunch of folks ready to be taught design patterns using C++. Keep up the good work.👍😊
What Can I say...Just the one which I wanted..Simple..Crisp..Clear.A Big Thumps UP
Thank you so much! ❤️😇
How to delete the object which dynamically created in im confused about deletion, we are having vehicle pointer and object created is different
I came to learn the factory design pattern and learnt how to create archive and object files too!! Wow
Really well explained i have seen multiple videos couldn't grasp the concept but u nailed it thanks a lot please do more video like this
With this if else you are polluting the Factory class as well. Imagine adding 10 more type of vehicles tomorrow. You have to maintain a registry of vehicle types added in a kind of hashmap. The key being the vehicle type, the value is the vehicle object.
Nice explanation.. the way you explained the concepts of factory pattern is different than others (through library creation)..hoping for more videos..
for remaining patterns advantages and drawback of using that pattern can also be discussed
I can tell you where Recently I have used this Pattern:
I have designed three classes:
1. GkeAgent
2. EksAgent
3. AksAgent
Interface: IKubernetesService
Implemeted Factory KubernetesServiceFactory.
Based on the Properlty file value of the cloud type i am returning the suitable object.
short crisp and to the point explanation
Kudos Keerti! This was really good!!
I'm familiar with some design patterns like this, and hence, could follow everything properly. But thinking from a beginner's perspective, it could have been better :)
Few observations:
1. The explanation was tightly coupled to C++. A person learning design patterns shouldn't have to start with the library creation approach, that too involving C++ commands. Those are extra details that can be picked up later, if needed. I feel like you could have gone with a more generic and simpler approach, especially since this is the "Simple Factory Pattern".
2. The video was kinda short. An in-depth explanation spanning half an hour would have been better. For instance, a comprehensive explanation could have been provided regarding the object creation approach, i.e., the reason behind doing Base B = new Child() instead of Child C = new Child() and its impacts since this acts as a prerequisite to understanding the factory approach.
Very nice observation and feedback 👍
I have one doubt of this kind of implementation of factory design pattern , I.e this code violate the open and closed principle of SOLID .
Because whenever you will be adding new condition in the factory method you will be modifying , but principle says you code should be open for extension and closed for modification. So how could you handle please explain.
@keerti can you please create videos explaining all design patterns as i don't find many design patterns easy to learn and adapt content. btw great job, you nailed the content on your channel. I am software engineer and currently pursuing masters from ASU and preparing for interviews for SDE2 roles.
@keerti thank you for responding back and today I hold SD3 offer from Oracle and have started job previous week. Thank you for motivating and influencing Relevant content. Much love 😍
Awesome explanation and one of the most simple explanation I have found on the Internet. Please include more videos
Thank you so much! ❤️😇
This is very underrated, please make more videos in the series. I am sure it will garner more views in the long term! :D
Nice explanation. Now i got cleared what factory pattern does.
In which of the scenarios would you use factory pattern and why?
Consuming a service
Complex Validation
Logging
Data Binding
None of the Above
The bike and car are stored in a vehicle reference. What if there are functions which are not present in vehicle class but are present in bike or car class (not talking about overridden functions)?
clarity at peaks :)
Hi Keerti, the client was still required to call createVehicle which i think could have been handled by the factory itself unless createVehicle is parameterised. Can you please explain why there is distinction between default constructor and createVehicle and what createVehicle is supposed to do?
thanks..!! your way of presention is awsome...getting desigin patterns in new and detailed wayy!!😊
I really love the way you explained....thanks for sharing play list.
Please make a detailed video on how to make linkedin profile so strong that recruiters of tech giant's approach freshers (2020passouts) for job openings.
i really like the way you explained. The example was not at all complex, simple vehicle objects work like charm. Would love to see a dedicated Design Pattern series which could help someone prep for OOD. Great Content.
Hi Keerti! Thanks for creating the playlist. If you could show the code in Java too, it would be more helpful.
Keerti saying "hi guys" is one of the few cutest things I experienced during a day🔥🔥
thanks for this video. but.. whenever we make any changes in our factory class (say we add bus class), then we do need to recompile the whole factory class, as well as ask client to update the factory jar which they are using.. so is there any way to overcome this as well in this design pattern ??
You can use dynamic library (dll/.so files), I think that should work.
What have you included in Vehicle.cpp 4:33?
Hey Keerti, I just watched the video and I was able to get the concepts and advantages that you talked about in the video but I struggled with the implementation part cuz most of the things were completely new for me. So, could you please suggest any resources for learning the implementation of libraries and header files in c++?
Extremely well explained.
Please make more of such videos explaining all design patterns with examples. This was very helpful
Thanks mam until I worked on cpp 98 version.now I started giving interviews.i faced questions on design patterns I don't how they work,how I want use in project ur videos help lot to understand concept and practical
Thank u mam a lot please do videos mam
Hi Keerti,
Great explanation.
I see some of createFactory classes include around 7-10 constructor arguments and pass the exact same or 1-2 more arguments to create the underlined class. It is little tightly coupled because does not give flexibility to accept new type of class in factory method, is this correct approach? To refactor, I think I can use ClassName as parameter in createFactory, and there will be additional 7-10 constructor arguments passed along.
Hi keerti,
I seen this factory design pattern video in that you create factory for separation of vehicle type. We can do that in stored procedure pass car, bike,truck, bus and get only those record and get faster execution can you give one more real time example
in first place you have not included vehicle oblect file vehicle.o in the vehicle liberary, you only added car & bike object file to library. Please explain
a very beginner friendly video. Nice explanation. One question - why we are not using the vehicle.o in creating the library ? Thanks in advance.
Thank you so much, i was struggling to understand this honestly
Simple and Nice Explanation , Waiting for New Lectures ,Thanku
this is a wonderful video on factory design pattern. loved it
How many total videos will be there in this series??
Atleast 20 different concepts was discussed. Took me 2 hours to complete this tutorial
watched the video but still can't figure it out what's its real usage. I am in the field of web development
I believe in the last code example the vehicle objects are actually getting created in the factory method getVehicle method. The name of the funtion in bike and car classes should be changed from create vehicle to something else.
Thanks for the nice explaination. One query: In this pattern, whose responsibility is it to destroy the created vehicle object ?
Could you please create video on ROR and basically using RSpec for writing test cases please Mam
Great Explanation ! Keep doing the videos.
Awesome video keep making 🔥.
Thanks keerti for sharing .. I'm eagerly waiting for all the videos in lld.
Great explanation and a great series. Thanks for all the efforts. Why did you stop this series though :(
I know I am super late but never stopped, had a lot going on in personal life. Uploaded the new video today and hoping to finish the series super soon. Hope you like the video!
Hi Keerthi, rather than going with the bookish / standard definition you have explained in in simple terms so that even novice programmer can understand. but I have a query here , you said that whenever there is a change in the requirement from the client we need to change the library and give it back to the client, I mean when client needs TEMPO vechile, we need to change the library and give it to him right ??
For your upcoming video please zoom into your code so that we can get a clear view of it .... Lots of love ❤️❤️ love your teaching and love your contents
Nice explanation and thank you fir using c++
Please also made video for rest patterns mainly behavioral once like strategy pattern..
thank you.. it helps us a lot. where can I find the code? did you upload in the git hub? can you please share the code paths?
U really made whole concept soo easy..thanks alot.
One request is it possible to make video on abstract factory.
It seems bit difficult for me to understand conceptually.
I understand when they give some example but still not able to understand when and where to use
I will cover all the design patterns, please do share the videos with your friends as well 😇😇
@@KeertiPurswani sure I will😊
Thank you very much for all your C++vedios. The videos are of great value. But, I still have question on factory design pattern.
With the VehicleFactory class introduced , we are making smartclient independent as the code for any new vehicle needs to be implemented in VehicleFactory. However, dependent library for smart client is changing and that needs to be delivered to client everytime a change is made right........
Where as without vehicleFactory client.exe should be rebuild by changing all the dependent libraries.
My question is in anycase client gets a new deliverable right....
Di you are doing a great job, pls make more videos .Greatly eager to learn 😊😊👍. Will share these videos too.!!
Hey Keerti just saw this video today and your explanation is pretty neat and understandable. Waiting for other design patterns and lld content
Excellent explanation keep growing...
Awesome simplified explanation Keerti! 🙂Please continue the series covering major design patterns using c++ code examples. Please give a thought about making a video series on C++ multithreading as well. Many thanks! Keep up the good work. 🙂
It was Really a good one to start with Design Patterns. Really Looking forward to this series.
It would be even more good if you add descriptive things to remember at the middle or end to make a note of it for future reference and also adding interview perspective to this. Thanks Keerti.
Why haven't we used vehicle.o while compiling the library?
Do continue this series! I really appreciate your effort 🙏🙏
Very easy to understand. Thank you.
If in future there is a need to add new vehicle type then developer needs to change in existing library.Doesnt it violates the Open/closed principle?
Very well explained 👍
I haven't found a link which point to code what we covered int this video, plz share code as well.
Thanks for this amazing video!
Nice explanation. But don't you think the if-else branching in your factory method will violate the Open Closed principle ?
Really Nice Explanation !
This is The Simple Factory pattern, not The Factory Design pattern. "The Simple Factory isn’t actually a Design Pattern; it’s more of a programming idiom." according to Head First Design Patterns. In addition, the use cases for the Simple Factory and Factory methods are not the same. The Factory method uses inheritance to provide a common framework; it does more than merely create objects.
Really great content. I will just request you to release other lectures soon, so that the continuity doesn't breaks. Thank you for sharing your knowledge..
good explanation mam😊
Amazing stuff!
Few points needs to make clear.
1. Why that factory class is made static if not then what would happen?
In real world scenrio is it done like this?
2. More examples related to real work.
The content length is good. Keep that but make it more advanced with focusing on low level design. 👍
The factory class is _not_ static - that was clarified several times in the video. Only the getVehicle() method is static. If it was not, you would have to create an instance of the factory before you could use the getVehicle() method.
Nicely explained .
Can I have the code for all this patterns ? Explanation is super..
Great explanation. Thankyou :)
Could you please help me understand what is there in vehicle.cpp file
Hi Keerthi I think u have explained simple factory which is not a design pattern...can u explain factory method design pattern
Amazing lecture .
But mam apko still jo first command hai gcc and all class name if age chal k truck ka class aya to usko bhi aapko gcc me lena hi padega so cpp me is that a problem or not I am not sure but
This design pattern definitely solves problem of object creations for above use case
Good explanation, thanks.
But doesn't it breaks the concept of Open Closed Principle because we are still modifying our VehicleFactory class. Please clear