Victor Brown

When I first started seeing blog posts and articles questioning the relationship between Cloud Computing and SOA…  I started wondering what was causing the confusion.  Were our definitions of Cloud Computing not clear? Were we not conveying the Cloud’s correct value proposition or its role in the enterprise?

I’ve come to the conclusion that it’s all of the above.

 SOA is an architecture paradigm and a set of principles to guide service-based applications, platforms, and even enterprises (SOE).  Cloud Computing is a computing platform paradigm that consolidates physical services into virtual shared services (infrastructure).  They don’t conflict or compete.  And they don’t enable each other.

SOA and Clouds Complement Each Other

They can, however, complement each other to create a whole that’s greater than the parts.

The confusion continues, however, and has grown to be a major topic of debate.  There are on-going discussions about the relationship between Cloud and SOA – claims that one requires the other; suppositions that SOA is dead because Cloud is the new service platform; analysis of the criteria that would determine if a business should adopt cloud or SOA.

For me, it became a serious issue recently when I was tasked by a client to address the question. I was asked to clarify the two paradigms’ value propositions, create a vision for how they can be leveraged together to create a service platform, and develop a roadmap to get there.

As an outgrowth of that initiative, I’ve started a series of posts on StrategicITArchitecture.com. My thesis is that Cloud and SOA can be combined to create the Ultimate Enterprise Service Platform. The series will frame the issues and present a set of recommendations and framework for developing a roadmap.

Check it out, if you’re interested, and please comment if you disagree, agree, or have suggestions.  You can also take a look at a scaled-down version of a Cloud/SOA presentation that I prepared for a client.

A lot of us have been using server virtualization for a few years now. We’re well aware of how effective a virtual platform can be when it comes to utilizing server resources. In my experience, clients have seen their server utilization go from an average of 5-15% to at least 60-75%. And the number of physical servers can be reduced by 50% to 70%, or more!

Of course, a robust virtualized platform is the foundation for virtually (cool pun!) all Cloud Computing – public clouds like Amazon and Google, or private corporate Clouds.

One really significant aspect of virtualization is the contribution that a virtualized IT platform makes to “Evergreen IT” – a term coined, I believe, by PriceWaterhouseCoopers. In addition to reducing the number of physical servers, which of course reduces electrical consumption and heat generation (less air conditioning), most Hypervisor systems can be configured to automatically shut down servers that aren’t needed during periods when less capacity is required.

During a recent lunch with a client’s VMWare representatives, I was treated to a good explanation of the latest green-IT features offered by their suite of products. Although I haven’t put them to the test, yet, it sounds pretty impressive – e.g., claims of as much as 80% reduction in use of electricity (supported by a Gartner report)!

Given all of the benefits that IT virtualization (and Cloud Computing) is demonstrating, it’s hard not to visualize a future for IT that’s built on information utilities. Obviously, in these early years… most large corporations will maintain their own internal “IT utilities” and will realize tremendous benefits by doing so. But eventually…. Will it make sense for even mega-users of IT resources not to tap into the commercial “IT power plants”?

Of course, I’m also the guy who wrote an article in 1985, for our leading IT trade publication, in which I predicted that the age of the software “factory” was imminent! I could see quite clearly that object oriented architectures and tools were about to bring an end to the long and painful process of reinventing software for every new product or application. Oops!

But this time…. The future not only looks pretty compelling, it’s being proven more and more viable at a rapid pace.

I was a Twitter skeptic!  I know… if you’re a Tweeter you’re thinking, “What a curmudgeon! How out of touch can you be?”  But, nevertheless, although I dabbled in the Twitter culture, I was slow to see any value. 

Now…  I have truly seen the light! Twitter has become an indispensible source of real-time news and information. But I know there are still many skeptics out there and I completely understand.  For me, a major breakthrough came when I realized that it was all about who/what sources you choose to follow.  For example, if you follow news sources (CNN, NYT, etc.) you get real-time news feeds. If you follow people in your profession, you get an early view of developments and a finger on the pulse of activity in your field.

Today I found an outstanding article in the New York Times, “Why Twitter Will Endure” (got it from a Tweet I received, of course), written by David Carr. (See http://bit.ly/4IpTAT) David does an outstanding job of explaining why Twitter has become such a key enabler for an informed and action-oriented lifestyle.

I posted the link to this article on Twitter, but that’s a lot like “preaching to the choir.” If you saw my Tweet…. then you’re using Twitter!  I’m sending this little piece to those of you who still don’t see any value in joining the Twitter community.

Many of you are no doubt considering some aspect of Cloud Computing in your Business and IT strategies for 2010. I’m sure you’re taking an incremental approach as you identify the best opportunities and the best approach for realizing the benefits that Cloud Computing can offer.

I’ve just posted some guidance for developing a Cloud Computing Roadmap on my Strategic IT Architecture Web site. Obviously, it’s a complex topic and there are many, many variations on the routes you might map out.

One approach that I didn’t mention in that post – space is limited in a blog posting – was an approach that mitigates and contains risk, while still delivering a solid foundation for internal Clouds and near-term ROI and operational benefits.  Server platform virtualization.

Virtualization is a mature and proven platform architecture that greatly improves asset utilization and can significantly enhance operational efficiency. Clouds are based on a virtualized platform.

In order to fully evolve into a Cloud, and provide all of the benefits that Clouds offer, you will eventually need to enhance the virtual environment with some additional capabilities – e.g., self provisioning, dynamic resource allocation, measured/metered usage. You’ll also want to make some enhancements to the platform architecture to better accommodate multi-tenancy, elasticity and other powerful Cloud capabilities.

But as a solid first step toward a Cloud Computing target, and as a means of containing risk – including the risk of moving core applications to an external, still unproven commercial Cloud – consider implementing a virtualized computing IT ecosystem.

One additional technical point: As you develop your implementation plan for a virtualized platform, you do need to consider what kind of “Hypervisor” you’ll use. The most critical decision is whether to use a Type 1 (bare metal) product or a Type 2 (hosted) Hypervisor.  Type 1 provides maximum performance because it executes on the hardware (bare metal) and provides its own operating system support. Type 2 is installed as a guest operating system on a hosted system, so it sacrifices some performance because it’s running in a layer above the native OS.

Clearly, we don’t all mean the same thing when we refer to the “Cloud”! That’s the first issue I encounter as I work with clients to identify the best and most suitable use of Cloud Computing –ambiguity and lack of precision in defining the term. Unfortunately, when there’s a discussion of Cloud Computing strategy it invariably focuses on one specific type of Cloud and the discussion and conclusions drawn from it are based on that very narrow definition.

Here’s a quote from a briefing that one of my clients used to kick off their Cloud strategy discussions. The definition is valid, but only for one specific model of Cloud Computing – public (commercial) clouds.

“Cloud computing refers to the practice of purchasing computer services that are stored and maintained by a third-party contractor, instead of housing all the equipment and software on-site.”

When this slide appeared on the screen, 10 minutes into the kickoff session, most of the leadership team reacted immediately. Their response, based on the misperception created by that focused and incomplete definition, was… we do not, and will not outsource our IT platforms to anyone!

It took a quickly improvised white-board session to clarify the opportunity and to get this initial strategy session back on track. There are tremendous benefits available from the use of an appropriate Cloud Computing model and its enabling technologies.

Examples of the strategically significant Cloud models are:

• Public Clouds (defined above) – examples include Google (e.g., GAE), Amazon (e.g., EC2, S3), and Microsoft Azure.
• Private Clouds – managed for the use and benefit of a single organization. Significant benefits from consolidation and virtualization of platforms and operations.
• Community Clouds – shared by multiple communities of interest. Benefits from pooling resources and operational costs.
• Hybrid Clouds – Consisting of Private Cloud(s) and augmented by integration with Public Clouds for “cloud bursting”, auxiliary data storage, or for access to commercial applications.

One common example where lack of specificity in the definition of the Cloud results in a misleading conclusion, the recurring argument that security is a major inhibitor to adopting Cloud Computing. This concern is only valid (to some degree) when referring to commercial Cloud vendors who have not, yet, reached security compliance. Growing maturity in this space and lessons learned have shown that multiple data centers, consolidated into a Private Cloud can be hardened, secured and managed to a much higher level and at lower cost than is possible across multiple data centers.

Bottom line: the potential benefits are significant. Just follow well-proven best practices – understand the problem space, clearly define goals, identify the risks, assess benefits (ROI being only one measure), identify the best, most appropriate solution (e.g., what’s the best Cloud model) – and you can craft an effective roadmap to reach your target. Significant benefits await!

If you’re interested, I’m discussing a more detailed approach to developing a Cloud Computing Roadmap on my Strategic Architecture blog at http://StrategicITArchitecture.com.

To state the obvious, cloud hype is extremely loud and distorted right now. As with most emerging technologies or computing paradigms, the rush by vendors to capitalize on (or, create) new opportunities and by enthusiastic early adopters to try to gain a competitive edge creates lots of confusion and silliness. (Maybe Gartner should have a “Silly Season” in their Hype Cycle!)

There is, of course, a great deal of value to be gleaned from the cloud movement – both from public cloud services and by implementing private/internal clouds. As cloud vendors and services mature, they will be a valuable addition to the IT landscape and will fill a variety of roles (some as core services and others as utility services). But enterprise users should not rush to try to realize the promised benefits without a clear strategy, realistic planning and – above all — risk management.

Just a brief comment about the etymology of the term “cloud. We used to use “cloud” as a symbol for some entity out on the network. We weren’t concerned with what was in that cloud (generally, it was a black box). Someone else was providing results/output from that we needed. It didn’t matter how the functionality was implemented as long as it delivered what we needed at the edge (contracts and other means of assuring the usability, quality and usefulness had to be in place, of course).

The cloud in “Cloud Computing” as we use the term today is quite different. These Clouds need to be grey boxes, not black boxes. We need to understand much more about their construction and how they operate. I strongly recommend that if you’re planning to host core processes or data in/on a cloud that’s managed and controlled by another party… you need to exercise due diligence and establish clear, contractual agreements on SLAs, ensure that security is appropriate for your use, and understand your data and process migration options — and that’s just for starters.

I’m elaborating more on this and other related topics to create a clear framework for a Cloud Computing Roadmap in my blog at http://www.StrategicITArchitecture.com.

Even though the potential benefits are obvious, and some early adopters are already experiencing a positive ROI, I fear for the near-term future of Cloud Computing!  (For a late-breaking ROI example see http://bit.ly/HDJVy)

It looks to me like we are very close to the peak of the Hype Cycle – lots of, often irrational, press; “silver bullet” claims; rush to adoption without attention to basic best practice (which will result in early failures that deepen the Trough of Disillusionment!).

Note: I’m referring here to enterprise cloud computing – private, community, and hybrid — not the simple SaaS offerings, like productivity tools. Generally, those are pretty low-risk with minimal impact/risk.

One of my concerns is the lack of clarity in definition, and overloading the use of the term, Cloud Computing. I do believe that we’ve established the foundation for clarity in understanding what Cloud Computing means and the options for leveraging the opportunities it offers (for more information, see http://www.StrategicITArchitecture.com). But it looks to me as if the momentum (frenzy?) has built to the point that many prospective adopters are not paying attention to basics and are rushing to judgment.

Clouds (in their various flavors) represent a powerful and positive evolution in our delivery and consumption of IT resources and services. Ensuring success in choice of strategy, reduction of risk, and the earliest possible ROI can benefit from tracking the Hype Cycle and factoring it into the decision making process. Prudent adoption strategies will ensure that we reach the Plateau of Productivity.

Clearly the economic challenges we’ve been facing over the past 18 months have been almost unprecedented. As business leaders, it’s been very difficult to plan and to know how to best use our scarce resources. But, as always, those who demonstrate creativity, leadership and courage can seize opportunities to focus on developing powerful IT strategies that position them for competitive advantage and growth as the economy continues to recover.

One of my favorite, recent articles in the McKinsey Quarterly is by Professor Richard Rumelt, UCLA, titled “Strategy in a structural break.” Rumelt makes a compelling case that we’re in the midst of a “structural break”, now, and suggests how we might craft strategies for seizing the inevitable opportunities that emerge from the chaos. For more about the implications to those of us who are IT leaders and professionals, see my blog at www.StrategicITArchitecture.com.

At a minimum, it may be possible to develop strategies that allow you to leverage — and maybe re-purpose — under-utilized assets already in place to create a more powerful, effective and agile IT ecosystem; minimum investment for maximum advantage. Cloud Computing – private, public, and hybrid Clouds — offers some interesting and exciting alternatives!

Welcome to my personal Web site. This is the first post to my new site since it’s been modified to a blog format!  I’m very excited because this new format will allow us to actually carry on a dialog.

Now… my challenge is to find some interesting and provocative topics that are worth the time and effort for you to engage.