Skip to main content

Abstract Factory Pattern

Abstract Factory Pattern 


Gamma Categorization: Creational Design Patten
Summary: When the object construction is complicated, needing multiple arguments, we should create a separate function (Factory Method) or class (Factory), which is responsible for the creation of the all object.

Problem examples

Suport of multiple databases
Multiple data sources: Serial port, ethernet port, device driver
Diferent report types

Solution

Abstract class
Generalized interface
A Factory creates instances of the concrete classes

Sample Code

The abstract factory

public interface IPhotoFactory
{
    IAnaloguePhoto CreateAnaloguePhoto();
    IDigitalPhoto CreateDigitalPhoto();
}


The abstract products

public interface IAnaloguePhoto
{
    string GetName();
}

public interface IDigitalPhoto
{
    string GetName();
}

The concrete factories
public class CanonFactory : IPhotoFactory
{
    public IAnaloguePhoto CreateAnaloguePhoto()
    {
        return new CanonAnaloguePhoto();
    }

    public IDigitalPhoto CreateDigitalPhoto()
    {
        return new CanonDigitalPhoto();
    }
}

public class NikonFactory : IPhotoFactory
{
    public IAnaloguePhoto CreateAnaloguePhoto()
    {
        return new NikonAnaloguePhoto();
    }

    public IDigitalPhoto CreateDigitalPhoto()
    {
        return new NikonDigitalPhoto();
    }
}

The concrete products

public class CanonAnaloguePhoto : IAnaloguePhoto
{
    public string GetName()
    {
        return "Canon Analogue Photo";
    }
}

public class CanonDigitalPhoto : IDigitalPhoto
{
    public string GetName()
    {
        return "Canon Digital Photo";
    } 
}

public class NikonAnaloguePhoto : IAnaloguePhoto
{
    public string GetName()
    {
        return "Nikon Analogue Photo";
    }
}

public class NikonDigitalPhoto : IDigitalPhoto
{
    public string GetName()
    {
        return "Nikon Digital Photo";
    } 
}

The client

public class PhotoClient
{
    public enum Brand { Canon, Nikon};

    private IPhotoFactory photoFactory;

    public PhotoClient(Brand brand)
    {
        switch (brand)
        {
            case Brand.Canon:
                photoFactory = new CanonFactory();
                break;
                case Brand.Nikon:
                photoFactory = new NikonFactory();
                break;
        }
    }

    public string GetAnaloguePhoto() => photoFactory.CreateAnaloguePhoto().GetName();
    public string GetDigitalPhoto() => photoFactory.CreateDigitalPhoto().GetName();
}

Usage

var photoClient = new PhotoClient(PhotoClient.Brand.Canon);
WriteLine(photoClient.GetAnaloguePhoto());
WriteLine(photoClient.GetDigitalPhoto());

photoClient = new PhotoClient(PhotoClient.Brand.Nikon);
WriteLine(photoClient.GetAnaloguePhoto());
WriteLine(photoClient.GetDigitalPhoto());

Comments

Post a Comment

Popular posts from this blog

XML Webservice (ASMX) - SOAP Request and Response Invocation logging

You are an integration developer. Eventualy you came into the state where there is nothing else you can debug, and you have to check which SOAP request it is built on the request, and which SOAP response you are getting from the server. C# XML Webservice (ASMX) - SOAP Request and Response Invocation logging In the legaccy .NET framework System.Web.Services , this means using soapExtensions to help you intersept the interaction with the webservice. This is done like so:  public class TraceExtension : SoapExtension     {         Stream oldStream;         Stream newStream;         string filename;         // Save the Stream representing the SOAP request or SOAP response into          // a local memory buffer.          public override Stream ChainStream(Stream stream)         {           ...
Post a Comment
Read more

SOLID (1/5) - Single Resposibility Principle

 SOLID (1/5) - Single Resposibility Principle The single-responsibility principle (SRP) is a computer-programming principle that states that every class in a computer program should have responsibility over a single part of that program's functionality, which it should encapsulate. All of that module, class or function's services should be narrowly aligned with that responsibility. In the following example we have a TodoList class which only handles it's own functionality logic, and then we have a Persistance class which handles the saving logic, hence keeping the concerns separeted. using   System ; using   System . Collections . Generic ; namespace   Journal {      public   class   TodoList     {          private   readonly   List < string >  _entries  =  new   List < string >();          private...
Post a Comment
Read more