Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

Creating the Services Directory 125
Deployment tools, including service deployment, typically through
binding with external development environments
Links to testing tools and services, providing the developer/designer the
ability to create a test plan and testing scenarios and then to leverage
service-testing technology
In essence, design time service governance works up from the data to the
services, gathering key information as it goes. You typically begin by defining
the underlying data schema and turning that into metadata and perhaps an
abstraction of the data. Then, working up from there, you further define the
services that interact with the data, data services, and then transactional services
on top of that. You can further define that into processes or orchestration.
All this occurs with design time information managed within the design
time service governance system.
Runtime service governance works and plays in the world of service management
and should be linked with design time service governance, but often
is not. Design time is all about defining the policies around the use of services.
Therefore, runtime governance is the process of enforcing and implementing
those policies at service runtime, but it may do other things as well.
Runtime service governance, like design time service governance, comes
in many flavors because of the number of vendors in that space and how it is
defined by that vendor. There are no de facto standards as to what runtime service
governance needs to be, but certain patterns are emerging.
Runtime service governance typically includes
Service discovery
Service delivery
Security
Setting and maintaining appropriate service levels
Managing errors and exceptions
Enabling online upgrades and versioning
Service validation
Auditing and logging