Content deleted Content added
clean up, remove promotional links, needs reliable sources |
m Open access bot: url-access updated in citation with #oabot. |
||
(20 intermediate revisions by 16 users not shown) | |||
Line 1:
{{Short description|Layered architectural pattern}}
{{One source|date=April 2010}}
'''Service
==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.
The [[Service Reusability Principle|service reusability]] principle dictates that services should be designed to maximize reuse. Similarly, the [[Service Composability Principle|service composability]] principle advocates designing services so that they can be composed
==Usage==
[[File:Service 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.]]
[[File:Service 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'>
Wajid Khattak [http://www.informit.com/articles/article.aspx?p=1583177 Service Layers] [Online].Date accessed: 21 April 2010.</ref>
An alternative layering from Bieberstein et al.,<ref>Bieberstein. et al.[
The service
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}}
* {{cite conference |display-authors=1 |last1=Mauro |first1=Christian |last2=Leimeister |first2=Jan Marco |last3=Krcmar |first3=Helmut |year=2010 |title=Service Oriented Device Integration - An Analysis of SOA Design Patterns |department=HICSS 2010 |work=2010 43rd Hawaii International Conference on System Sciences |pages=1–10 |doi=10.1109/HICSS.2010.336 |isbn=978-1-4244-5509-6 |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}}
*
*
▲* www.binaryspectrum.com.[http://www.binaryspectrum.com/service-oriented_architecture/soa_and_Java_2.html Service-Oriented Architecture and Java - Service Layer][Online].Date accessed: 17 April 2010.
* {{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}}
▲* Norbert Bieberstein, Keith Jones, Robert G. Laird, Tilak Mitra.[http://www.informit.com/articles/article.aspx?p=1194198 Executing SOA: A Methodology for Service Modeling and Design][Online].Date accessed: 17 April 2010.
== External links ==
* [
[[Category:Service-oriented (business computing)]]
|