12.07.2015 Views

Migration of a Chosen Architectural Pattern to Service Oriented ...

Migration of a Chosen Architectural Pattern to Service Oriented ...

Migration of a Chosen Architectural Pattern to Service Oriented ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 3. <strong>Architectural</strong> <strong>Pattern</strong>s 44Layer – A layer encapsulates common logic on the same level <strong>of</strong> abstraction.Each layer provides an interface allowing another layer <strong>to</strong> cal its functionality.Relationships – A layer can use other layer only if they are connected.There are uni and bi directional relations between layers. This pattern ischaracterized by lack <strong>of</strong> direct calls <strong>of</strong> layers <strong>to</strong> non-neighbor layers. If thelayer number one wants <strong>to</strong> call the method from the layer number threeand there is no direct connection between them, the layer number one has<strong>to</strong> call the layer number two in order <strong>to</strong> call the layer number three. Alayer can invoke only a layer that is bellow or above this layer. Connectionlimited <strong>to</strong> only upper and lower layer increases maintainability but reducesperformance (see figure 3.6).Layer 1Layer 2Layer 3Figure 3.6: Example usage <strong>of</strong> Layer pattern2. Pipe and filtersOverview – The pattern is characterized by a good and efficient way <strong>of</strong>data processing but the structure <strong>of</strong> the pattern reduces its reliability becauseif one <strong>of</strong> the filters fails, the whole process fails as well.ElementsFilter – processes data. A filter can push data <strong>to</strong> a pipe or pull it out froma pipe.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!