This glossary supports the following titles:
SOA Design Patterns
Web Service Contract Design & Versioning for SOA
SOA Principles of Service Design
Service-Oriented Architecture: Concepts, Technology, and Design
Modern SOA Infrastructure: Technology, Design, and Governance
SOA with REST
Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing
SOA with .NET & Azure
SOA with Java
SOA Governance
SOA Security: Practices, Patterns, and Technologies for Securing Services
SOA and Cloud Computing: Practices, Patterns, Technologies
This glossary also supports the SOA Certified Professional (SOACP) program.
For more information, visit: www.soacp.com
and
www.soaschool.com
|
|
|
runtime autonomy
|
The level of control a service has over its processing logic at the time the service is invoked and executing is called runtime autonomy.
The Service Autonomy design principle advocates increasing runtime autonomy in order to guarantee the following to service consumers:
• consistently acceptable runtime execution performance
• a greater degree of performance reliability
• the option for it to be isolated in response to specific security, reliability,
or performance requirements
• a greater level of behavioral predictability (especially when concurrently accessed)
The more a service is comprised of logic or resources that are shared by other parts of the enterprise, the less it is able to make the types of quality of service claims just
listed.
The primary reason these claims are so important to service-orientation is service composition. Because a composition exists as an aggregate of programs (services) that may also be participating in other compositions, it tends to be naturally non-autonomous.
See also:
- design-time autonomy
- Service Autonomy
- service composition
- Service Loose Coupling
|
|
