Service layer pattern: Difference between revisions

Revision as of 15:14, 13 March 2010

Revision as of 15:16, 13 March 2010

Line 11:

==Usage==

<br/>

[[Image:SOA_DP_Service_Layers_Image_AService_Layers_Image_A.JPG|thumb|alt=Diagram A|Diagram A<br/>In the absence of any layers, services contain a mixture of different types of logic. This makes it difficult to manage these services.]]

[[Image:SOA_DP_Service_Layers_Image_BService_Layers_Image_B.JPG|thumb|alt=Diagram B|Diagram B<br/>A service inventory divided into layers where each layer contains the same type of logic.]]

In order to apply this pattern, first it needs to be established which different types of layers are required. This requires creating a [http://www.soamethodology.com/p2.php service inventory blueprint]: a pool of services consisting of candidate services containing candidate functionality. By creating such an inventory, enough information is available to find out the different types of functionality within the intended service inventory. Based on this information, the required types of layers can be established. On the other hand, by applying this pattern at this stage within the service delivery process, the design of the service can be modified so that it contains the relevant type of logic as dictated by the type of the service layer under which this particular service falls.

<br/>