Service composability principle: Difference between revisions

Revision as of 00:37, 17 January 2016

Revision as of 15:42, 20 January 2016

Line 6:

The concept of developing software out of independently existing components encourages the concept of composition. This is the underlying concept within object-orientation where the end product is composed of several interlinked objects that have the ability to become part of multiple software solutions, no matter how complex the solution is. The same composition concept is inherited by service-orientation, whereby a business process is automated by combining multiple services. However, within service-orientation there is even greater focus on building services that can be composed and recomposed within multiple solutions to provide the [[agility]] promised by the SOA. As a result of this emphasis, some guidelines are required to develop services that can be effectively aggregated into multiple solutions.

The service composability principle provides design considerations that help towards designing composable services with a view to encourage service reuse as much as possible. The guidelines providesprovided by this principle prepare the service so that it is ready to participate in service compositions without requiring any further design changes.

==Application==