Ben Northrop

Decisions and software development

Pattern's Group Questions > Abstract Factory

November 11th, 2006


Provide an interface for creating families of related or dependent objects without specifying their concrete classes.-Design Patterns, GoF




  1. How does the Abstract Factory pattern support the principle of implementing to an interface, not a class?
  2. What are some typical product families that are encountered in an enterprise application?How often are they exchanged?
  3. If products are often added or removed, what is the impact, given this pattern?
  4. Is there ever overlap between product families? How could you support this, given the pattern?
  5. What happens if one product family has a slightly different set of products?

Examples Which are Abstract Factories?

  1. Core J2EE Design Patterns Abstract DAO Factory


I believe that software development is fundamentally about making decisions, and so this is what I write about (mostly). I've been building software for about 20 years now, as a developer, tech lead, and architect. I have two degrees from Carnegie Mellon University, most recently one in philosophy (thesis here). I live in Pittsburgh, PA with my wife, 3 energetic boys, and dog. Subscribe here or write me at ben dot northrop at gmail dot com.

Got a Comment?

Sign up to hear about the next post!

If you liked this article and want to hear about the next one, enter your email below. I don't spam - you'll only receive an email when there's a new post (which is about once a month, tops). It's all low-key, straight from me.

Comments ()

 None so far!