Uploaded October 2012 | Updated September 2026, 1 week ago
You can find a sample application at the link below
matlusstorage.blob.core.windows.net/uploads/DomainFacade.zip
The Layered architecture (architectural pattern) is a common pattern employed by many. However more often than not the layers are not really layers in that separating out the business layer and data layer into separate assemblies does NOT make for a "layer".
In this presentation, I introduce you to the layered architecture and it's virtues along with tenets of the layered architecture pattern while introducing the Domain Façade pattern that makes it very simple to form a virtual boundary (or layer).
The Domain Façade essentially has one single responsibility and that is: Coordinate (or Orchestrate) complex internal functions. In addition to it responsibility, what you get from employing this pattern in your layered architecture are a few other benefits:
1. The Domain Façade defines the boundaries of your layers (domain layer, data layer etc.)
2. Allows the core (The classes in the layer but "behind" the façade) to evolve independently from the API.
3. Reduces negative coupling
4. The interface of the Façade (i.e. the public methods of the class) defines the API of the layer or the set of available operations.
You can find a sample application at the link below
matlusstorage.blob.core.windows.net/uploads/DomainFacade.zip
The Layered architecture (architectural pattern) is a common pattern employed by many. However more often than not the layers are not really layers in that separating out the business layer and data layer into separate assemblies does NOT make for a "layer".
In this presentation, I introduce you to the layered architecture and it's virtues along with tenets of the layered architecture pattern while introducing the Domain Façade pattern that makes it very simple to form a virtual boundary (or layer).
The Domain Façade essentially has one single responsibility and that is: Coordinate (or Orchestrate) complex internal functions. In addition to it responsibility, what you get from employing this pattern in your layered architecture are a few other benefits:
1. The Domain Façade defines the boundaries of your layers (domain layer, data layer etc.)
2. Allows the core (The classes in the layer but "behind" the façade) to evolve independently from the API.
3. Reduces negative coupling
4. The interface of the Façade (i.e. the public methods of the class) defines the API of the layer or the set of available operations.
