Abstract Factory
Provides an interface for creating families of related objects without specifying their concrete classes.
errorWhat Problem Does the Abstract Factory Pattern Solve?
Applications often need to create groups of related objects that must be used together (e.g., UI components for a specific OS theme). Creating these objects independently risks mixing incompatible products and scatters creation logic throughout the codebase.
check_circleHow the Abstract Factory Pattern Works
Define an abstract factory interface with a creation method for each product in the family. Concrete factories implement this interface to produce products that belong together. Client code receives a factory and calls its methods, never knowing which concrete classes are instantiated.
Abstract Factory Pattern Architecture
Rendering diagram...
Implementation by Language
Abstract Factory Pattern in the Real World
“Imagine furnishing a room from IKEA versus a luxury boutique. Each store (factory) produces a complete set of furniture — chairs, tables, sofas — that share a consistent style. You pick the store, and every piece you get matches. You never mix a rustic IKEA chair with a baroque boutique table.”
Frequently Asked Questions
helpWhat is a real-world example of Abstract Factory?
UI toolkit libraries are a classic example. A WindowsUIFactory creates Windows-styled buttons, checkboxes, and menus, while a MacUIFactory creates Mac-styled versions. The client code works with the abstract factory interface and never references platform-specific classes directly.
helpHow does Abstract Factory relate to Dependency Injection?
Abstract Factory is one way to implement DI for object creation. Instead of injecting individual objects, you inject a factory that knows how to create an entire family of related objects. DI containers often use this pattern internally to manage object graphs.