09.02.2015 Views

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 ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

It’s All about the Bus<strong>in</strong>ess 79<br />

4. The amount of money, if any, that can be saved us<strong>in</strong>g these improvements.<br />

5. Soft benefits.<br />

6. Hard benefits.<br />

7. Holistic impact on the bus<strong>in</strong>ess, good <strong>and</strong> bad.<br />

8. F<strong>in</strong>al proposed budget.<br />

9. Suggestions for mov<strong>in</strong>g forward, or the ability for the <strong>SOA</strong> us<strong>in</strong>g cloud<br />

comput<strong>in</strong>g to benefit the bus<strong>in</strong>ess, or not.<br />

It’s All about the Bus<strong>in</strong>ess<br />

While few will dispute the bus<strong>in</strong>ess value of <strong>SOA</strong> us<strong>in</strong>g cloud comput<strong>in</strong>g,<br />

there is always a need to create a bus<strong>in</strong>ess case that def<strong>in</strong>es the value for a<br />

specific bus<strong>in</strong>ess. In most cases, you will f<strong>in</strong>d that cloud comput<strong>in</strong>g has a<br />

clear bus<strong>in</strong>ess value, but there are those cases where it does not, <strong>and</strong> thus it<br />

should not be used. You will not know until you def<strong>in</strong>e the bus<strong>in</strong>ess case <strong>and</strong><br />

run the numbers.<br />

One th<strong>in</strong>g to keep <strong>in</strong> m<strong>in</strong>d is that cloud comput<strong>in</strong>g is not free, <strong>and</strong> you<br />

have to consider the impact on IT holistically. Watch out for what is called<br />

the manage-by-magaz<strong>in</strong>e effect, where cloud comput<strong>in</strong>g is so much a part of<br />

popular th<strong>in</strong>k<strong>in</strong>g around comput<strong>in</strong>g that you are not objective. It is okay to<br />

say no to cloud comput<strong>in</strong>g if there is no clear bus<strong>in</strong>ess benefit. Also, cloud<br />

comput<strong>in</strong>g is clearly an architectural option for <strong>SOA</strong>. While you can do <strong>SOA</strong><br />

without cloud comput<strong>in</strong>g, you cannot do cloud comput<strong>in</strong>g without <strong>SOA</strong>.<br />

Keep that <strong>in</strong> m<strong>in</strong>d.<br />

What is go<strong>in</strong>g to be difficult is creat<strong>in</strong>g bus<strong>in</strong>ess cases as the world of<br />

cloud comput<strong>in</strong>g cont<strong>in</strong>ues to emerge. Simply put, we just do not know<br />

enough about cloud comput<strong>in</strong>g’s long-term operational value or many of the<br />

pitfalls that may arise, s<strong>in</strong>ce most of the public cloud comput<strong>in</strong>g providers<br />

that we are likely to leverage have not been around for all that long. You always<br />

need to consider this as a learn<strong>in</strong>g process, <strong>and</strong> make sure to look at the<br />

current state-of-the-art while leverag<strong>in</strong>g the guidel<strong>in</strong>es we put forth <strong>in</strong> this<br />

book. The technology will constantly change. The architecture should be relatively<br />

stable.<br />

On the upside, we have a clear opportunity to change the way we do IT<br />

to have a more positive <strong>in</strong>fluence on the bus<strong>in</strong>ess when leverag<strong>in</strong>g an <strong>SOA</strong><br />

us<strong>in</strong>g cloud comput<strong>in</strong>g. No longer will IT be a dra<strong>in</strong> on company resources,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!