What is the difference between Factory and Strategy patterns?

by

A factory pattern is a creational pattern. A strategy pattern is an operational pattern. Put another way, a factory pattern is used to create objects of a specific type. A strategy pattern is use to perform an operation (or set of operations) in a particular manner. In the classic example, a factory might create different types of Animals: Dog, Cat, Tiger, while a strategy pattern would perform particular actions, for example, Move; using Run, Walk, or Lope strategies.

In fact the two can be used together. For example, you may have a factory that creates your business objects. It may use different strategies based on the persistence medium. If your data is stored locally in XML it would use one strategy. If the data were remote in a different database, it would use another.

More Related Contents:

  1. Real World Example of the Strategy Pattern
  2. How to avoid ‘instanceof’ when implementing factory design pattern?
  3. Finding a good design pattern for Java
  4. Design Patterns web based applications [closed]
  5. Singletons vs. Application Context in Android?
  6. Implementing Singleton with an Enum (in Java)
  7. Design Patterns: Factory vs Factory method vs Abstract Factory
  8. What is the solution for the N+1 issue in JPA and Hibernate?
  9. Long list of if statements in Java
  10. Use Cases and Examples of GoF Decorator Pattern for IO
  11. Spring AOP vs AspectJ
  12. Builder Pattern in Effective Java
  13. Best way to build a Plugin system with Java
  14. Visitor pattern’s purpose with examples [duplicate]
  15. Is it bad practice to make a setter return “this”?
  16. Other Ways of Singleton in Java [duplicate]
  17. Open Session In View Pattern
  18. How to get all classes names in a package? [duplicate]
  19. In simplest terms, what is a factory?
  20. Why does every object in Java implicitly extend java.lang.Object class?
  21. Benefits and drawbacks of method chaining and a possibility to replace all void return parameters by the object itself
  22. Is This Use of the “instanceof” Operator Considered Bad Design?
  23. Why people use message/event buses in their code? [closed]
  24. Singleton pattern (Bill Pugh’s solution)
  25. Why Java allows increasing the visibility of protected methods in child class?
  26. What is the difference between a fluent interface and the Builder pattern?
  27. How to create a singleton class
  28. How to hide the internal structure of a Java API to the rest of the world
  29. Law of Demeter with data model objects
  30. Template design pattern in JDK, could not find a method defining set of methods to be executed in order

Leave a Comment