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.
222 Chapter 12 Mov<strong>in</strong>g Onward<br />
code level. Conceptual st<strong>and</strong>ards that are noth<strong>in</strong>g but white papers are<br />
worthless.<br />
St<strong>and</strong>ards should be <strong>in</strong> wide use. This means that many projects leverage<br />
this st<strong>and</strong>ard <strong>and</strong> the technology that uses the st<strong>and</strong>ard, <strong>and</strong> they are<br />
successful with both. In many <strong>in</strong>stances, st<strong>and</strong>ards are still concepts <strong>and</strong><br />
not yet leveraged by technology consumers.<br />
St<strong>and</strong>ards should be driven by the end users, not by the vendors. At least,<br />
that’s the way it should be <strong>in</strong> a perfect world. While the vendors may<br />
have had a h<strong>and</strong> <strong>in</strong> creat<strong>in</strong>g the st<strong>and</strong>ards, the consumers of the technology<br />
should be the ones driv<strong>in</strong>g the def<strong>in</strong>ition <strong>and</strong> direction. St<strong>and</strong>ards<br />
that are def<strong>in</strong>ed <strong>and</strong> ma<strong>in</strong>ta<strong>in</strong>ed by vendors often fail to capture the<br />
hearts <strong>and</strong> m<strong>in</strong>ds, while st<strong>and</strong>ards ma<strong>in</strong>ta<strong>in</strong>ed by technology consumers<br />
typically provide more value for the end user <strong>and</strong> thus live a longer life.<br />
The key advice here is to not let st<strong>and</strong>ards drive your architecture. Leverage<br />
them where they are needed to support the architecture. The architecture<br />
should be fairly stable, while the technology <strong>and</strong> the enabl<strong>in</strong>g st<strong>and</strong>ards will<br />
surely change over time.<br />
Q: How will <strong>SOA</strong> <strong>and</strong> cloud comput<strong>in</strong>g exist together <strong>in</strong> the future<br />
A: Let’s get back to the basics. <strong>SOA</strong> is an architectural pattern that actually<br />
predates the <strong>SOA</strong> buzzword. It is about break<strong>in</strong>g architecture down to a<br />
functional primitive, underst<strong>and</strong><strong>in</strong>g the <strong>in</strong>formation <strong>and</strong> behaviors, <strong>and</strong><br />
build<strong>in</strong>g it up aga<strong>in</strong> us<strong>in</strong>g service <strong>in</strong>terfaces that are abstracted <strong>in</strong>to a configuration<br />
layer to create <strong>and</strong>, more importantly, re-create bus<strong>in</strong>ess solutions.<br />
<strong>SOA</strong>, as the A implies, is architecture.<br />
<strong>Cloud</strong> comput<strong>in</strong>g is a platform option, or a way of creat<strong>in</strong>g a system <strong>in</strong><br />
which some or all of its IT resources exist with<strong>in</strong> some third-party cloud<br />
comput<strong>in</strong>g resource, such as Amazon EC2 (an <strong>in</strong>frastructure-as-a-service) or<br />
Force.com (a platform-as-a-service). <strong>Cloud</strong> comput<strong>in</strong>g is someth<strong>in</strong>g that<br />
can <strong>in</strong>volve part or all of an architecture.<br />
<strong>Cloud</strong> comput<strong>in</strong>g is an architectural option, but it is not architecture<br />
unto itself. This will not change as we move forward. <strong>SOA</strong> should become<br />
even more important to this emerg<strong>in</strong>g space because it provides guidance as<br />
to how the architectures are formed <strong>and</strong> which target platforms are the correct<br />
fit, on-premise <strong>and</strong> cloud comput<strong>in</strong>g–based.