Factory Method Patterns in C#

Factory Method Patterns

Definition: In Factory pattern, we create object without exposing the creation logic. In this pattern, an interface is used for creating an object, but let subclass decide which class to instantiate. The creation of object is done when it is required. The Factory method allows a class later instantiation to subclasses.

Uses of Factory Method Patterns

1.    creation of object is done when it is required.

2.    The process of objects creation is required to centralize within the application.

3.    A class (creator) will not know what classes it will be required to create.

interface Product

{

}

class ConcreteProductA : Product

{

}

class ConcreteProductB : Product

{

}

abstract class Creator

{

 public abstract Product FactoryMethod(string type);

}

class ConcreteCreator : Creator

{

 public override Product FactoryMethod(string type)

 {

 switch (type)

 {

 case "A": return new ConcreteProductA();

 case "B": return new ConcreteProductB();

 default: throw new ArgumentException("Invalid type", "type");

 }

 }

}

Factory method pattern falls under Creational Pattern of Gang of Four (GOF) Design Patterns in .Net. It is used to create objects. People usually use this pattern as the standard way to create objects. In this article, I would like share what is factory pattern and how is it work?

What is Factory Method Pattern?

In Factory pattern, we create object without exposing the creation logic. In this pattern, an interface is used for creating an object, but let subclass decide which class to instantiate. The creation of object is done when it is required. The Factory method allows a class later instantiation to subclasses.

Factory Method Pattern - UML Diagram & Implementation

The UML class diagram for the implementation of the factory method design pattern is given below:

The classes, interfaces and objects in the above UML class diagram are as follows:

1. Product

   This is an interface for creating the objects.

2. ConcreteProduct

   This is a class which implements the Product interface.

3. Creator

   This is an abstract class and declares the factory method, which returns an object of type Product.

4. ConcreteCreator

   This is a class which implements the Creator class and overrides the factory method to return an instance of a ConcreteProduct.

C# - Implementation Code

interface Product
{
 
}
 
class ConcreteProductA : Product
{
}
 
class ConcreteProductB : Product
{
}
 
abstract class Creator
{
 public abstract Product FactoryMethod(string type);
}
 
class ConcreteCreator : Creator
{
 public override Product FactoryMethod(string type)
 {
 switch (type)
 {
 case "A": return new ConcreteProductA();
 case "B": return new ConcreteProductB();
 default: throw new ArgumentException("Invalid type", "type");
 }
 }
}

Factory Method Pattern - Example

Who is what?

The classes, interfaces and objects in the above class diagram can be identified as follows:

1. IFactory - Interface
2. Scooter & Bike - Concreate Product classes
3. VehicleFactory - Creator
4. ConcreteVehicleFactory - Concreate Creator

C# - Sample Code

using System;
namespace Factory
{
 /// <summary>
 /// The 'Product' interface
 /// </summary>
 public interface IFactory
 {
 void Drive(int miles);
 }
 
 /// <summary>
 /// A 'ConcreteProduct' class
 /// </summary>
 public class Scooter : IFactory
 {
 public void Drive(int miles)
 {
 Console.WriteLine("Drive the Scooter : " + miles.ToString() + "km");
 }
 }
 
 /// <summary>
 /// A 'ConcreteProduct' class
 /// </summary>
 public class Bike : IFactory
 {
 public void Drive(int miles)
 {
 Console.WriteLine("Drive the Bike : " + miles.ToString() + "km");
 }
 }
 
 /// <summary>
 /// The Creator Abstract Class
 /// </summary>
 public abstract class VehicleFactory
 {
 public abstract IFactory GetVehicle(string Vehicle);
 
 }
 
 /// <summary>
 /// A 'ConcreteCreator' class
 /// </summary>
 public class ConcreteVehicleFactory : VehicleFactory
 {
 public override IFactory GetVehicle(string Vehicle)
 {
 switch (Vehicle)
 {
 case "Scooter":
 return new Scooter();
 case "Bike":
 return new Bike();
 default:
 throw new ApplicationException(string.Format("Vehicle '{0}' cannot be created", Vehicle));
 }
 }
 
 }
 
 /// <summary>
 /// Factory Pattern Demo
 /// </summary>
 class Program
 {
 static void Main(string[] args)
 {
 VehicleFactory factory = new ConcreteVehicleFactory();
 
 IFactory scooter = factory.GetVehicle("Scooter");
 scooter.Drive(10);
 
 IFactory bike = factory.GetVehicle("Bike");
 bike.Drive(20);
 
 Console.ReadKey();
 
 }
 }
}

Factory Pattern Demo - Output

When to use it?

1. Subclasses figure out what objects should be created.
2. Parent class allows later instantiation to subclasses means the creation of object is done when it is required.
3. The process of objects creation is required to centralize within the application.
4. A class (creator) will not know what classes it will be required to create.