title: What are the differences between Abstract Factory and Factory design patterns?
body: <p>I know there are many posts out there about the differences between these two patterns, but there are a few things that I cannot find.</p>
  
  <p>From what I have been reading, I see that the factory method pattern allows you to define how to create a single concrete product but hiding the implementation from the client as they will see a generic product. My first question is about the abstract factory. Is its role to allow you to create families of concrete objects in (that can depend on what specific factory you use) rather than just a single concrete object? Does the abstract factory only return one very large object or many objects depending on what methods you call?</p>
  
  <p>My final two questions are about a single quote that I cannot fully understand that I have seen in numerous places:</p>
  
  <blockquote>
    <p>One difference between the two is that
    with the Abstract Factory pattern, a
    class delegates the responsibility of
    object instantiation to another object
    via composition whereas the Factory
    Method pattern uses inheritance and
    relies on a subclass to handle the
    desired object instantiation.</p>
  </blockquote>
  
  <p>My understanding is that the factory method pattern has a Creator interface that will make the ConcreteCreator be in charge of knowing which ConcreteProduct to instantiate. Is this what it means by using inheritance to handle object instantiation?</p>
  
  <p>Now with regards to that quote, how exactly does the Abstract Factory pattern delegate the responsibility of object instantiation to another object via composition? What does this mean? It looks like the Abstract Factory pattern also uses inheritance to do the construction process as well in my eyes, but then again I am still learning about these patterns.</p>
  
  <p>Any help especially with the last question, would be greatly appreciated. </p>