Skip to main content

Facade Pattern

Facade Pattern 


Gamma Categorization: Structural Design Pattern
Summary: Provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the subsystem easier to use.

Sample Code

Problem: We want a facade for our digital camera subsystems.

public class DigitalCameraFacade
{
    ICamera camera;        
    IStorageManager storageManager;
    INetworkManager networkManager;

    public DigitalCameraFacade(ICamera cameraIStorageManager storageManagerINetworkManager networkManager)
    {
        this.camera = camera;            
        this.storageManager = storageManager;
        this.networkManager = networkManager;
    }

    public void TakePhoto()
    {
        var photo = camera.TakePhoto();
        storageManager.WriteFile(photo);
        networkManager.Send(photo);
    }
}

public interface ICamera
{
    byte[] TakePhoto();
}

public class DSLR : ICamera
{
    public byte[] TakePhoto()
    {
        System.Console.WriteLine("Taking photo.");
        return new byte[1024];
    }
}

public interface IStorageManager
{
    byte[] ReadFile();
    void WriteFile(byte[] file);        
}

public class SDCardManager : IStorageManager
{
    public byte[] ReadFile()
    {
        System.Console.WriteLine("Reading file to drive.");
        return new byte[1024];
    }
    public void WriteFile(byte[] file) => System.Console.WriteLine("Writing file from drive.");
}

public interface INetworkManager
{
    void Connect();
    void Send(byte[] file);
}

public class WifiManager : INetworkManager
{
    public void Connect() => System.Console.WriteLine("Connecting.");
    public void Send(byte[] file) => System.Console.WriteLine("Sending file.");
}

Usage

var digitalCamera = new DigitalCameraFacade(new DSLR(), new SDCardManager(), new WifiManager());
digitalCamera.TakePhoto();

Output

Taking photo.
Writing file from drive.
Sending file.

Comments

Popular posts from this blog

C# Extension Methods

 C# Extension Methods Extension methods      public   static   class   ExtensionMethods     {          public   static   Stopwatch   Measure ( this   Func < int >  f )         {              var   sw  =  new   Stopwatch ();              sw . Start ();              f ();              sw . Stop ();              return   sw ;         }          public   static   void   Save ( this   ISerializable   s...

SOLID (4/5) - Interface segregation principle

Interface segregation principle In the field of software engineering, the interface-segregation principle (ISP) states that no client should be forced to depend on methods it does not use. ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them. Such shrunken interfaces are also called role interfaces. ISP is intended to keep a system decoupled and thus easier to refactor, change, and redeploy. using   System ; namespace   interfacesegregation {      public   class   Document       {     }      public   interface   IMachine       {          void   Print ( Document   d );          void   Scan ( Document   d );     ...

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...