|
|
| John Lorenzo Bautista | It is an autonomous, reusable, discoverable, stateless functionality that has the necessary granularity, and can be part of a composite application or a composite service.
A reusable service should be identified with a business activity described by the service specifications (design-time contract).
A service’s constraints, including security, QoS, SLA, usage policies, may be defined by multiple run-time contracts, multiple interfaces (the WSDL for a SOAP Web Service), and multiple implementations (the code).
For more information about this concept, please check this post from ORACLE explaining reusable service in SOA: http://www.oracle.com/technetwork/articles/bechara-reusable-service-087796.html | 2014-03-27 15:51 | + |
|
|