Revision as of 18:10, 21 April 2010 edit The constant contributor (talk \| contribs) 488 edits added text + citation ← Previous edit		Revision as of 18:10, 21 April 2010 edit undo The constant contributor (talk \| contribs) 488 edits mNo edit summary Next edit →
Line 1: '''Service Composability''' is a design principle, applied within the [[service-orientation]] [[Design_paradigm\|design paradigm]], which encourages the design of [[Service (computer science)\|services]] in a manner so that they can be reused in multiple solutions that are themselves made up of composed services. The ability of the service to be recomposed should be independent of the size and complexity of the service composition<ref name='servicecomposition'>[http://www.whatissoa.com/p12.php Service Composition]</ref>. <br/> :This principle is directly related to 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>. ==Purpose==

Service composability principle: Difference between revisions