As you remember from Part 1 of this article series, there are 17 steps to
Assess the business. Assess the culture. Assess the value. Understand your
data. Understand your services. Understand your processes. Understand the
cloud resources. Identify candidate data. Identify candidate services.
Identify candidate processes. Create a governance strategy. Create a security
strategy. Bind candidate services to data and processes. Relocate services,
processes, and information. Implement security. Implement governance.
We covered the first two, so let's continue down the list.
Assess the Value
What will cloud computing bring to your bottom line? That's what we will
determine in this step. In essence, this is the process of calculating the
ROI for the formations of clouds around your enterprise. However, keep in
mind that not al... (more)
With the advent of Web services and SOA, we've been seeking to create
architectures and systems that are more loosely coupled. Loosely coupled
systems provide many advantages including support for late or dynamically
binding to other components while running, and can mediate the difference in
the component's structure, security model, protocols, and semantics, thus
This is in contrast to compile-time or runtime binding, which requires that
you bind the components at compile time or runtime (synchronous calls),
respectively, and also requires that changes ... (more)
The use of APIs pervades the emerging world of cloud computing. People find
they can mix and match information from all sorts of sources to create an
application that specifically meets their needs. Indeed, companies such as
The Web Service are in the business of providing you with key business data
through Web service-based APIs, along with other players out there.
However, a missing piece has been the ability to leverage your data through
such an API without forcing you to get into the API enablement business.
Considering this: The Web Service has launched a new service cal... (more)
It has come to my attention that there are really two kinds of SOA technology
vendors out there, old school and new school - each offering very different
approaches to solving the SOA problem. I'm not going to mention any
particular vendors, but you guys can guess who they are.
Keep in mind, what's important here is that not any particular approach or
technology is correct, but that the approaches and technologies you employ
match up with your requirements and business expectations. However, it's also
important to understand exactly the type of technology you're going to
Here we go again. While the paint is still wet on this new Web 2.0 stuff,
many SOA vendors and large analysts firms are calling their market SOA 2.0.
It's one of the silliest things I've heard in a long while, and both the
analysts and vendors who use this term should be ashamed of themselves.
I get Web 2.0 because the Web is well over 10-years-old and we've been
successful in using this pervasive technology and now we're moving to newer
and more exciting stuff such as AJAX and RSS thus the new version number.
However, we've yet to get large-scale traction with SOA so SOA 2.0 is ... (more)