Cloud Computing – Where to Start?

I have been asked a lot about the where/what/why/when/how one should start when addressing the need to adopt cloud computing within an organization. This is one of those questions that has many right answers and few wrong ones. The only wrong answer that I would address, for right now, is the “not addressing it at all” argument. Given the transformational nature of cloud computing (it has an impact on software, operations, sales, marketing, etc.), it is important to at least raise the question for discussion. With that wrong direction aside, let’s look at one right direction that will help management gain a perspective on at least the “what.”

Your leadership could benefit from understanding how our products/services map into the cloud computing space. A simple way to do this is to take an inventory of our offerings and map it to a Cloud Computing Reference Model (CCRM or C2RM).

A quick side note – while there are no formal C2RMs, the NIST (National Institute of Standards and Technology) is promoting a version that seems to make sense many practitioners in this field. This particular version categorizes the cloud along subscribers/supplies, SaaS, App-comp/PaaS/IaaS, and Physical Infrastructure. While I will discuss this model in more detail later, for now it looks pretty complete, with the exception of addressing internal vs. external cloud computing characteristics.

Using this model, your organization can allocate each solution to a service level. You also want to cross categorize it as a function of external cloud (e.g., Amazon, Force, etc.) and internal cloud (e.g., IBM, etc.). For example, using the external cloud for QA testing of your products often makes sense (External Cloud.Amazon EC2.Your Product). For many organizations, you probably won’t think about getting in the Platform as a Service space (Internal Cloud.Platform as a Service.Some Scriptable Platform), but using external cloud PaaS providers, like Force.com, should be considered (External Cloud.Platform as a Service.Force). But for which application(s) and how they should integrate with external/internal supplies, is an important question to be flushed out in later analyses.

Keep in mind, as you go through this process, which is one of many, the initial allocation should be based on high level business propositions (revenue/margin increase, cost reduction), that will later be vetted more completely. This kind of asset mapping is one of the first parts of developing a comprehensive top down driven cloud computing strategy. Understanding where you fit in the reference model and how it will further promote our business interests is essential if we want to make the cloud more than just a passing fad. Make sense?

~ by Dr. J on July 8, 2009.