Service composability principle: Difference between revisions

Revision as of 02:50, 25 June 2016

Revision as of 09:28, 8 September 2016

Line 1:

In computing, '''Serviceservice 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'>[http://www.whatissoa.com/p12.php Service Composition]</ref>

This principle is directly responsible for the agility promised by SOA as it promotes composing new solutions by reusing existing services.<ref name='MP'>Michael Poulin.[http://www.ebizq.net/blogs/service_oriented/2009/02/evolution_of_principles_of_service_orientation_service_statelessness_part_6.php Evolution of principles of Service Orientation: Service Statelessness, part 7][Online].Date accessed: 21 April 2010.</ref>