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 ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
When <strong>Cloud</strong> <strong>Comput<strong>in</strong>g</strong> Fits 187<br />
processes, <strong>and</strong> data must be extensively changed. Further, as events <strong>and</strong> circumstances<br />
evolve over time, any change to any architectural component dem<strong>and</strong>s<br />
a correspond<strong>in</strong>g change to the tightly coupled component as well.<br />
When the Po<strong>in</strong>ts of Integration Are Well Def<strong>in</strong>ed<br />
Architectural components placed on cloud comput<strong>in</strong>g platforms should have<br />
well-def<strong>in</strong>ed <strong>in</strong>terfaces to <strong>in</strong>tegrate those components back to on-premise<br />
components—services, data, or processes or complete applications made up of<br />
those components. The architecture should also have the ability to l<strong>in</strong>k its<br />
components to other cloud-based systems, such as <strong>in</strong>frastructure-as-a-service,<br />
platform-as-a-service, <strong>and</strong> database-as-a-service. The better the po<strong>in</strong>t of <strong>in</strong>tegration<br />
for an architectural component, the better that component can live <strong>in</strong> a<br />
distributed world.<br />
Anyth<strong>in</strong>g placed on a cloud comput<strong>in</strong>g platform should have the ability<br />
to be easily <strong>in</strong>tegrated with on-premise or other cloud comput<strong>in</strong>g–based systems<br />
<strong>and</strong> thus with well-def<strong>in</strong>ed <strong>in</strong>terfaces, such as APIs. Architects <strong>and</strong> developers<br />
can then b<strong>in</strong>d these systems leverag<strong>in</strong>g loosely coupled <strong>in</strong>tegration<br />
mechanisms, such as Web Services, <strong>and</strong> allow<strong>in</strong>g them to seamlessly work together<br />
to create a holistic architecture that supports the free flow of <strong>in</strong>formation<br />
along with the ability to <strong>in</strong>voke services or b<strong>in</strong>d them us<strong>in</strong>g processes. If<br />
the <strong>in</strong>terfaces are not well def<strong>in</strong>ed, then <strong>in</strong>tegration is more difficult, perhaps<br />
even impossible, so plac<strong>in</strong>g them on cloud comput<strong>in</strong>g platforms will be less<br />
than productive.<br />
When a Lower Level of Security Will Work Just F<strong>in</strong>e<br />
A lower level of security will work just f<strong>in</strong>e when we are not plac<strong>in</strong>g highly<br />
sensitive data on cloud comput<strong>in</strong>g platforms <strong>and</strong> thereby putt<strong>in</strong>g the bus<strong>in</strong>ess<br />
at risk. This does not mean that cloud comput<strong>in</strong>g–based systems cannot<br />
be secure, leverag<strong>in</strong>g state-of-the-art security approaches, st<strong>and</strong>ards, <strong>and</strong> enabl<strong>in</strong>g<br />
technology. However, consider<strong>in</strong>g sensitivity <strong>and</strong> compliance issues,<br />
some <strong>in</strong>formation is not a good fit to exist outside of the firewall.<br />
Some data, such as government secrets, are just too sensitive to be placed<br />
on cloud comput<strong>in</strong>g platforms because those platforms, even those with a<br />
high degree of security, are not wholly controlled by IT. You have to use your<br />
own judgment, consider<strong>in</strong>g the <strong>in</strong>formation <strong>and</strong> the consequences if it were