Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
124 Chapter 6 Work<strong>in</strong>g from <strong>Your</strong> Services to the <strong>Cloud</strong>s<br />
The directory must be the master directory for the entire architecture spann<strong>in</strong>g<br />
on-premise <strong>and</strong> the clouds, which eventually becomes the registry.<br />
In more sophisticated cloud comput<strong>in</strong>g solutions, the services directory is<br />
becom<strong>in</strong>g the axis mundi, able to access both the source <strong>and</strong> target systems <strong>in</strong><br />
order to discover necessary <strong>in</strong>formation (such as metadata <strong>and</strong> available bus<strong>in</strong>ess<br />
processes). Engaged <strong>in</strong> this “autodiscovery,” the <strong>SOA</strong> solution can populate<br />
the directory with this or any other <strong>in</strong>formation that may be required.<br />
Ultimately, the services directory will become the enterprise metadata repository,<br />
able to track all systems, services, <strong>and</strong> <strong>in</strong>formation, on-premise or on the<br />
cloud-delivered platforms.<br />
The value of a services directory should be clear. With the directory as a<br />
common reference po<strong>in</strong>t for all connected processes, services, <strong>and</strong> databases,<br />
<strong>in</strong>tegrat<strong>in</strong>g data <strong>and</strong> services is straightforward. The services directory can<br />
also track the rules that the architect <strong>and</strong> developer apply with<strong>in</strong> the <strong>SOA</strong><br />
problem doma<strong>in</strong>.<br />
Consider Service Governance<br />
One of the th<strong>in</strong>gs that is often forgotten when look<strong>in</strong>g at <strong>SOA</strong> us<strong>in</strong>g cloud comput<strong>in</strong>g<br />
is the notion of services governance, which is covered more extensively<br />
<strong>in</strong> Chapter 8, “Br<strong>in</strong>g<strong>in</strong>g Governance to the <strong>Cloud</strong>s.” From <strong>SOA</strong> governance, service<br />
governance is basically the same concept, or the ability to track, manage,<br />
<strong>and</strong> control the use of services that span on-premise <strong>and</strong> cloud-based systems.<br />
There are two types of service governance: design time <strong>and</strong> runtime.<br />
Design time service governance, as the name implies, typically provides an<br />
<strong>in</strong>tegrated registry/repository that attempts to manage a service from its<br />
design to its deployment, but typically not dur<strong>in</strong>g runtime execution of the<br />
services, albeit some do.<br />
Key components of design time service governance <strong>in</strong>clude<br />
A registry <strong>and</strong>/or repository for track<strong>in</strong>g service design, management,<br />
policy, security, <strong>and</strong> test<strong>in</strong>g artifacts<br />
Design tools, <strong>in</strong>clud<strong>in</strong>g service model<strong>in</strong>g, dependency track<strong>in</strong>g, policy<br />
creation <strong>and</strong> management, <strong>and</strong> other tools that assist <strong>in</strong> the design of<br />
services