pattern-factory-method

Decouple domain object creation by abstracting instantiation through factory methods, replacing direct `new ConcreteClass()` calls with creator subclasses that validate invariants before returning concrete domain entities.

Use the Factory Method pattern when refactoring domain service initialization or extensible entity construction requiring subclass-specific instantiation logic and polymorphic contracts to prevent rigid dependencies.

Refactor entity creation by building concrete creators that override a factory method to return specific domain entities, encapsulating construction logic and validating invariants before the product interface returns the object.

Yes, the Factory Method pattern requires product interfaces with polymorphic contracts so callers remain agnostic to concrete types, ensuring all products implement a shared contract validated by creators before instantiation.

The best way to handle extensible entity construction is applying the Factory Method pattern, using concrete creators to override instantiation logic and validate invariants while maintaining a shared product interface for polymorphic access.

Direct instantiation causes tight coupling in domain-driven design because clients depend rigidly on concrete classes, preventing flexible validation of invariants or subclass-specific instantiation logic before domain entities like BusinessUnit are created.