Composability is the ability of services to be used in orchestration scenarios by higher level services or processes. It is a special case of the reusability characteristic in that the services need to be uniform as well as reusable. The reason for this primary reason for this requirement is that the orchestrating service will in all probability but built using something like BPEL not a conventional programming language, so any variations in service style become more difficult to deal with.
Showing posts with label Consumer. Show all posts
Showing posts with label Consumer. Show all posts
Wednesday, 22 October 2008
Friday, 17 October 2008
What is SOA - Service Characteristics - Autonomous
A service is autonomous if it has full control over its internal logic. This requires that it has clearly defined and isolated (decoupled) functional and operational boundaries, that it is independent of other services and only communicates via contract-driven messages and policies.
A consumer should exercise no influence over the service other than to execute it and to provide input values. The service should have minimal dependency on its execution environment.
A consumer should exercise no influence over the service other than to execute it and to provide input values. The service should have minimal dependency on its execution environment.