Service composability principle: Difference between revisions

Revision as of 17:51, 13 February 2020

Latest revision as of 11:30, 26 January 2023

(2 intermediate revisions by 2 users not shown)

Line 1:

{{Short description|Computing design principle}}

In computing, '''service composability''' is a design principle, applied within the [[service-orientation]] [[design paradigm]], that encourages the design of [[Service (computer science)|services]] that can be reused in multiple solutions that are themselves made up of composed services. The ability to recompose the service is ideally independent of the size and complexity of the service composition.<ref name='servicecomposition'>{{cite web|url=http://www.whatissoa.com/p12.php|title=Service Composition|publisher=|access-date=2010-03-04|archive-url=https://web.archive.org/web/20100311045214/http://www.whatissoa.com/p12.php|archive-date=2010-03-11|url-status=dead}}</ref>

Line 26 ⟶ 28:

* Support for exception handling.

* The availability of meta-data about service capabilities and behavior.

==See also==

*[[Executable choreography]]

*[[Service choreography]]

== References ==

{{Reflist}}

* Kjell-Sverre Jerijærvi.[http://www.infoq.com/articles/soa-contract-maturity-model SOA Contract Maturity Model][Online].Date accessed: 21 April 2010.

* Mauro. et al. [https://wwwweb.webcitationarchive.org/5wB4T8QrA?url=web/20110203194511/http://www.computer.org/portal/web/csdl/doi/10.1109/HICSS.2010.336 Service Oriented Device Integration - An Analysis of SOA Design Patterns.] [Online], pp.&nbsp;1–10, 2010 43rd Hawaii International Conference on System Sciences, 2010. Date accessed: 8 April 2010.

* Dino Esposito.[http://msdn.microsoft.com/en-us/magazine/cc699560.aspx The HTML Message Pattern][Online].Date accessed: 21 April 2010.

* [[Service-oriented_architecture#Principles|Service-orientation Principles]]