Service layer pattern: Difference between revisions

Revision as of 10:51, 17 April 2010

Latest revision as of 14:39, 24 May 2025

(44 intermediate revisions by 26 users not shown)

Line 1:

{{Short description|Layered architectural pattern}}

{{Mergeto|Service layer|date=April 2010}}

{{Copyedit|date=April 2010}}

{{One source|date=April 2010}}

'''Service Layerslayer''' is aan [[Design_pattern_(computer_science)|designarchitectural pattern]], applied within the [[service-orientation]] [[Design_paradigm|design paradigm]], which aims to organize the services<ref name='services'>[http://www.whatissoa.com/p11.php services]</ref>, within a service inventory<ref name='serviceinventory'>[http://www.whatissoa.com/p13.php service inventory]</ref>, into a set of logical layers. Services that are categorized into a particular layer share the same type of functionality. This helps to reduce the governanceconceptual burdenoverhead related to managing the service inventory, as the services belonging to the same layer only containaddress a particularsmaller typeset of solution logic and as a result are easy to maintainactivities.

==Rationale==

Grouping services into functional layers reduces the impact of change. Most changes affect only the layer in which they're made, with few side-effects that impact other layers. This fundamentally simplifies service maintenance.

As more and more services are added to a service inventory, the management of services within the service inventory gets difficult. In an unorganized service inventory, just by having a look at a service, it’s very hard to predict what kind of functionality is contained in it. This further makes it difficult to pickup the right type of service until all of its functions are reviewed. Similarly, a service can be designed in a manner that it contains both the reusable logic as well as the process-specific logic. When it comes to change the process-specific logic, this can inadvertently impact the reusable logic as well, which means that the reusability potential of such a service is reduced. Contrary to this, the [[Service Reusability Principle|Service Reusability]] design principle dictates that services should be designed in a manner so that they can be reused as much as possible. Similarly, the [[Service Composability Principle|Service Composability]] design principle advocate designing services in a manner so that they can be composed into multiple service compositions<ref name='servicecompositions'>[http://www.whatissoa.com/p12.php service compositions]</ref>. Both of these qualities are only possible if the service only contains a specific type of logic e.g. either reusable logic or process-specific logic.

<br/>

InThe order[[Service toReusability designPrinciple|service areusability]] serviceprinciple sodictates that itservices containsshould abe particulardesigned typeto ofmaximize logicreuse. Similarly, differentthe logical[[Service groupsComposability ofPrinciple|service composability]] principle advocates designing services needso tothat they can be establishedcomposed withinin various ways. Both principles require that a service inventorycontain asonly advocateda byspecific the applicationtype of thelogic Servicee.g., Layerseither designreusable or process-specific patternlogic.<ref name='SOAMag'>[[Thomas Erl]].[http://soa.sys-con.com/node/645271?page=0,1 Introducing SOA Design Pattern] [Online]. Date accessed:6 April 2010.</ref>. EachRestricting groupeach only contains a particular type of logic, so by restricting the servicelayer to only contain a particular type of functionality, simplifies the design of the service remains rather straightforward and one can predict the type of functionality the service provides and its behavior by looking at which layer does it belong to e.g. services in a particular group may not be suitable for composition as compared to another group.

==Usage==

[[ImageFile: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.]]

[[ImageFile: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.]]

Applying this pattern requires creating a service inventory blueprint, a list of services with associated functionality. Next, group the services into layers according to function. Adopting a common layering strategy across the enterprise facilitates reuse in other applications, because developers don't have as much to learn (or invent) when they join a project. One common layering uses task, [[Entity Abstraction Pattern|entity]] and [[Utility Abstraction Pattern|utility]].<ref name='WK'>

In order to apply this pattern, first it needs to be established which different types of layers are required. This requires creating a service inventory blueprint<ref name='serviceinventoryblueprint'>[http://www.soamethodology.com/p2.php service inventory blueprint]</ref>: 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.

Wajid Khattak [http://www.informit.com/articles/article.aspx?p=1583177 Service Layers] [Online].Date accessed: 21 April 2010.</ref>

<br/>

Although service grouping can be performed based different types of functionalities, however, to keep the grouping standardized across the enterprise, the actual groups can be based on established service models<ref name='service models'>[http://www.soamethodology.com/p5.php service models]</ref> that depict the most common types of logic that services would normally contain. Depending upon the particular area of the business, a service inventory would usually be divided into task<ref name='task'>[http://www.soamethodology.com/p7.php Task Service]</ref>, entity<ref name='entity'>[http://www.soamethodology.com/p6.php Entity Service]</ref> and utility<ref name='utility'>[http://www.soamethodology.com/p8.php Utility Service]</ref> services. Each of these different types of service models bear specific characteristics that would be eventually demonstrated by the services that belong to the layer, which is based on a particular service model. To design a service based on the aforementioned service models the Process Abstraction<ref name='ProcessAbstraction'>[http://www.soapatterns.org/process_abstraction.php Process Abstraction]</ref>, the [[Entity Abstraction Pattern|Entity Abstraction]] and the [[Utility Abstraction Pattern|Utility Abstraction]] design patterns can be applied as these design patterns help in structuring the solution logic of the services according to specific types.

An alternative layering from Bieberstein et al.,<ref>Bieberstein. et al.[https://books.google.com/books?id=NISyExeJ5mAC&pg=PA88&dq=%22service+layer%22&lr=&hl=sv#PPA87,M1 Service-oriented Architecture Compass: Business Value, Planning, and Enterprise Roadmap].FT Press, 2005. {{ISBN|0-13-187002-5}}, {{ISBN|978-0-13-187002-4}}</ref> involves five layers, namely enterprise, process, service, component and object.

The application of the Service Layers pattern would necessitate a change in the architecture of the service and the overall architecture of the service inventory<ref name="SvcArch">[[Service-Oriented_Architecture_Types|SOA Types]]</ref>.

The service layer pattern invokes a specific [[Service-oriented architecture types|service architecture]].

==Considerations==

The application of this design pattern depends upon having enough knowledge about the kind of services in a service inventory before they are actually developed. Consequently, a [[Top-down_and_bottom-up_design|top-down]] service delivery approach<ref name="TopDown">[http://www.soamethodology.com/p9.php Top-Down Service Delivery Approach]</ref> needs to be adopted so that a pool of candidate services exists from which the need for different service layers can be established. This will increase the time and efforts required to actually deliver a set of usable services. Secondly, the confidence with which the need for different types of service layers can be established is directly proportional to the size of the service inventory. This means that as more and more services are added to the service inventory, the already established service layers may need to be modified in case new services do not fit into these existing service layers.

The [[Top-down and bottom-up design|top-down]] service delivery approach facilitates the use of this pattern.

== See also ==

* [[Service layer]]

== References ==

{{Reflist}}

* {{cite book |author-link1=Thomas Erl |last1=Erl |first1=Thomas |year=2009 |title=SOA Design Patterns |publisher=[[Prentice Hall]] |isbn=978-0-13-613516-6}}

* Erl et al,(2009).[http://www.amazon.com/gp/product/0136135161/ref=s9_simi_gw_p14_i1?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=center-1&pf_rd_r=0FBSA23BKC0AXWVZ5Q9G&pf_rd_t=101&pf_rd_p=51471022&pf_rd_i=507846 SOA Design Patterns]. Prentice Hall. ISBN 0136135161.

* {{cite conference |display-authors=1 |last1=Mauro. et|first1=Christian al.|last2=Leimeister [http://www.computer.org/portal/web/csdl/doi/10.1109/HICSS.|first2=Jan Marco |last3=Krcmar |first3=Helmut |year=2010.336 |title=Service Oriented Device Integration - An Analysis of SOA Design Patterns.] [Online],|department=HICSS pp.1-10,2010 |work=2010 43rd Hawaii International Conference on System Sciences, |pages=1–10 |doi=10.1109/HICSS.2010.336 Date accessed: |isbn=978-1-4244-5509-6 April|issn=1530-1605 |url=https://doi.ieeecomputersociety.org/10.1109/HICSS.2010.336 |accessdate=2020-07-26|url-access=subscription }}

* {{cite web |last1=Seshadri |first1=Srikanth |date=2007-01-17 |df=dmy |url=https://www.infoworld.com/article/2077670/logically-soa.html |title=Logically SOA |work=[[JavaWorld]] |accessdate=2020-07-26}}

* Dave Oliver.[http://geekswithblogs.net/SabotsShell/archive/2006/07/11/84708.aspx SOA Logical Model][Online].Date accessed: 17 April 2010.

* {{cite web |url=http://www.binaryspectrum.com/service-oriented_architecture/soa_and_Java_2.html |title=Service-Oriented Architecture and Java - Service Layer |department=Technology |publisher=Binary Spectrum |accessdate=2020-07-26}}

* {{cite web |last1=Bieberstein |first1=Norbert |last2=Jones |first2=Keith |last3=Laird |first3=Robert G. |last4=Mitra |first4=Tilak |date=2008-07-17 |df=dmy |url=https://www.informit.com/articles/article.aspx?p=1194198 |title=Executing SOA: A Methodology for Service Modeling and Design |work=[[InformIT]] |accessdate=2020-07-26}}

* {{cite web |url=https://collaboration.opengroup.org/projects/soa-book/pages.php?action=show&ggid=1334 |title=High-Level Perspective of the SOA RA |work=SOA Source Book |publisher=[[The Open Group]] |accessdate=2020-07-26}}

== External links ==

* [https://web.archive.org/web/20201111163522/https://patterns.arcitura.com/soa-patterns SOA Design Patterns]

* [http://www.whatissoa.com/ SOA Concepts]

* [http://www.soaglossary.com/ SOA Terms Glossary]

* [http://www.soapatterns.org SOA Design Patterns]

[[Category:Service-oriented (business computing)]]