The factory class is used by DocumentExtractor as shown in Listing 3.

Yes, they seem to be same but they do have a visible difference.

Yes, they seem to be same but they do have a visible difference.

Now let us check the program to understand both of them. The code to use the appropriate implementation of StatementExtractor based on document type is now present in StatementExtractorFactory as shown in Listing 2. Inheritance is used to achieve all benefits of OOP (it eventually leads to better readbility\maintainability\structure of code). Strategy with Factory Method design pattern. Conceptually it seems different, factory is used for differed instantiation of similar group of classes. Factory pattern is used to introduce loose coupling between objects as the factory will take care of all the instantiation logic hiding it from the clients. The client refers to the abstract creator class but uses one of the sub-classes to get the actual instance. So the name Factory Method Pattern. The factory class is used by DocumentExtractor as shown in Listing 3. In first example we are creating object of something, so we can conclude factory pattern is a creational pattern. Now let us check the program to understand both of them. So the name Factory Method Pattern. In the preceding, abstract method M() creates the actual instance and returns the reference to the client. The responsibility of creating the instance is delegated to the sub-class methods. In the preceding, abstract method M() creates the actual instance and returns the reference to the client. Now let us check the program to understand both of them. The responsibility of creating the instance is delegated to the sub-class methods. Inheritance. As i see it, although both are creational patterns, factory and prototype patterns are used in different contexts. Inheritance is used to achieve all benefits of OOP (it eventually leads to better readbility\maintainability\structure of code). Difference between Strategy Pattern and Factory Pattern? The difference lies in the usage of two examples above. Both patterns use "new" keyword to return an object(factory) or return and algorithm(strategy). But when i see their examples together, they look quite similar. Strategy is implemented using (or to support) Inheritance (actually, interface generalization). Factory's sole purpose is to create objects and strategy's sole intent to is to provide a mechanism to select different algorithm. For. Factory Design Pattern … where as Strategy is used for switching between algorithms. In second example it is clear we are trying to achieve a goal / execute a method based on input, hence strategy pattern is an operational pattern. Strategy is a pattern of OOP and Inheritance is a principle of OOP. Is there any major difference between Strategy Pattern and Factory Pattern? Strategy is implemented using (or to support) Inheritance (actually, interface generalization). The difference lies in the usage of two examples above. The client refers to the abstract creator class but uses one of the sub-classes to get the actual instance. Factory's sole purpose is to create objects and strategy's sole intent to is to provide a mechanism to select different algorithm. The difference lies in the usage of two examples above. The strategy design pattern (also known as the policy design pattern) is a behavioral design pattern that allows us to select an algorithm at runtime. Prototype pattern on the other hand is used when the cost of creating an object is large and it is ok to copy an existing instance than creating a new instance. The client refers to the abstract creator class but uses one of the sub-classes to get the actual instance. Conceptually it seems different, factory is used for differed instantiation of similar group of classes. Inheritance. Strategy is a pattern of OOP and Inheritance is a principle of OOP. You can use "factory" to create objects of "strategy". Both patterns use "new" keyword to return an object(factory) or return and algorithm(strategy). The responsibility of creating the instance is delegated to the sub-class methods. As for me its look alike and I am a bit confused which to use when. Factory pattern is used to introduce loose coupling between objects as the factory will take care of all the instantiation logic hiding it from the clients.