Service composability principle: Difference between revisions

Revision as of 22:34, 28 June 2022

Latest revision as of 11:30, 26 January 2023

(One intermediate revision by the same user 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 ==