🔥Abstract Design Pattern in Hindi | Important Question for Interview | Design Pattern Series
HTML-код
- Опубликовано: 22 май 2023
- Premium Course Library: courses.learncodewithdurgesh.com
In this video we are going to learn about abstract design pattern in detail step by step . first we will understand the concept and then we code.
Full Playlist: • Design Patterns Tutori...
Telegram Link for Doubt: t.me/learncodewithdurgesh
Important Videos:
➡️React JS with Project : • 🔥 🔥 Complete React Js ...
➡️Learn JDBC in one video: • JDBC Crash Course in 1...
➡️Learn Python in One Video: • Learn Python in One Vi...
➡️Learn HTML in one video: • Jquery in one video in...
➡️Learn HTML form in one video: • Jquery in one video in...
➡️Learn JavaScript in one videos: • Learn JavaScript in O...
➡️Learn Form Validation using javascript and jquery: • Form Validation using ...
➡️Learn CSS in one video: • Jquery in one video in...
➡️Jquery in one video: • Jquery in one video in...
Kotlin is one video: • Kotlin | Learn Kotlin ...
➡️Complete Python Project - RUclips downloader in one video: • Jquery in one video in...
Important Playlist:
➡️Spring Boot Tutorial with Project : • Spring Boot Tutorial i...
➡️Spring MVC Tutorial: • Spring MVC Tutorial St...
➡️Complete Spring Framework Tutorial: • Spring Framework Tutor...
➡️Hibernate Tutorials: • Hibernate Tutorial for...
➡️E-Commerce Project using Java: • E-Commerce Project usi...
➡️AWS Free Java Hosting Playlist: • AWS Hosting Tutorial |...
➡️Hibernate Tutorial Playlist: • Hibernate Tutorial for...
➡️Learn Technology in One Vides: • Learn in one video : C...
➡️Programming Tips for Programmers: • Coding Tips and Discus...
➡️Complete Python for Beginners: • Complete Python Tutori...
➡️Important Python Projects: • Python Projects in Hindi
➡️Complete Servlet & JSP : • Servlet and Jsp (Serve...
➡️Complete JDBC ( Java Database Connectivity) : • JDBC(Java Database Con...
➡️Complete Java Project : TechBlog: • Full Java Advance Pro...
➡️Java Swing Projects: • Java Projects for begi...
➡️Java Core Concepts: • Java Core Tutorial
➡️Kya aap Jante hai Series: • kya app jante hai : s...
Important Links:
👉Official Website (Source Code): learncodewithdurgesh.com/
👉Telegram Discussion Group: t.me/learncodewithdurgesh
👉Follow me on Instagram: / durgesh_k_t
👉Follow on Facebook / learncodewithdurgesh
Disclaimer:
All videos are for educational purposes and use them wisely. Any video may have a slight mistake, please take decisions based on your research. This video is not forcing anything on you.
![Chuckyy - Devil Hours [Official Music Video]](http://i.ytimg.com/vi/f3wZGj0VnZU/mqdefault.jpg)
I watched your video's since long good work ... really appreciated !
I have open point about this Abstract Factory Design Pattern. Why we are creating this Abstract Factory design patten is not because of Factory of Factory.
main reason behind it, Normal Factory design pattern ( Employee Factory) violates the rule of single responsibility/OpenClose Principle. ( assume there is another developer comes in future which is frontend developer, then we agin create a one more if condition in EmployeeFactory class, that is not a good practice.
so this abstract Factory design pattern resolve this issue now we are open for extension and close for modification if any new class introduced like frontend developer simply we extends the abstract class and provide implementation in new class or return object from their concrete class.
Basically abstract Factory design pattern belong to Dependency Inversion : class should depend upon abstract class or interface rather than concrete class.
If I have to pass the name of the factory then it is hardcoding and hence tightly coupled. For example (20:29 minutes) like you have passed new AndroidDevFactory() in line 7 then it's tightly coupled. Isn't it similar like getting directly new object by writing new AndroidDeveloper():
What are we exactly achieving here by creating so many multiple classes and making it complex?
Please correct me on the above and expecting a reply for better understanding.
same thing I thought
First of all whatever explained in this video is Factory method patterns but not Abstract Factory pattern. Coming to the point you asked about how does it different directly creating AndroidDev using new key word with respect to passing its Factory object to the main Factory. This is the main point to be addressed in the Factory Method Pattern. This whole Factory Method design pattern make sense only when we have any or some of the below requirements. Otherwise, Factory Method Patterns is of no use.
(Requirement 1) When you dont want to give object instantiation privileges to the user due to the security reasons. This make sense only when you are passing some information as params to the object which you are creating (AndroidDev) which you get from frameword or enviroment or clients account.
(Requirement 2) When the actual new AndroidDev is ony half way of getting a real state of object what client expects. Ex: after new AndroidDev, you might want to call some method like emp.takeInductionTraining() and then pass it to the client. You can do that in the Main Factory then pass it the client.
(Requirement 3) The actual parameters you need to pass to the new AndroidDev might not be availble in the client program and you get that from other places and then call new AndroidDev in main Factory class (obviosly in that case, Main Factory whuold be abstract instead of interface to provide such additional stuff. you get that from ruclips.net/video/TdJatgto5cU/видео.htmlsi=JF5VWcQoFZukng_w
The term Factories of Factory is used because
Factory DP - violating SRP and O/C Principle.
But Abstract Factory DP solves the above issue by a creating factory for each type of employee.
Correct me If I'm wrong.
Unfortunately thats not the case. Abstract Factory's main property is that a factory we use shold be in a position to create familiy of related objects, whic is not happening here. So this is not the correct explanation for Abstract Factory. Whatever he explained here is Factory Method. Please refer ruclips.net/video/5hXZnI86E2Y/видео.htmlsi=Q0BPVWHEJ6_7scBC here one TypeOfUniversityFactory is capable of creating its AdminCard object as well as FeeCalculatorObject (Multiple Objects) for an University. You an extend that for many more objects like UniverityBooks object. LibraryCard object etc. All such objects belong to one University.
First video of urs which I found confusing till now
TAKE A BOW from a 20 years ex. software engineer. Noone can teach simpler than this in world. PERIOD. Guru ho app.
Explanation with great examples. Useful
Sir, itna ache se bate ho...Thanks ....U r really makes complex topics ...so simple to understand.
great video
good work sir
Whats the benefit any how we writing classconstructor like previous
Employee e1 = new Androiddevloper();
First view , like and comment
I'm not getting one thing u said on 1:36 that we need to create object of employee but u take employee as interface right , but we can not create object of interface
Please make videos on data structures and algorithms with Java
❤
explanation is confusing, you are just copying from javatpoint
Hi Durgesh, Thanks a lot for all of your knowledge that you have shared till now. One request is there if you create one video of important questions and answers for interview from design pattern topics. As this area is large and vast.
notes link please
🔥🔥
Sir ji DSA bhi padha do
Please provide the source code for this. Or note.md file.
Please DSA ki bhi video padha do
core java ka v recorded de do durgesh courses me
Notes kaha milenge?
Sir can we get notes on this design pattern tutorial
+1
Dusri video bnao isme clarity se samaj nahi aaya aap bhaut accha smjate ho par yaha aache se clear nahi hua
👍
26 minutes video. 13 minutes explanation and 13 minutes for correcting spelling mistake.😁
Nice bus Bhai door me oil dal wa lo mai dar Gaya wo awaz se😂
🤣🤣
❤