What you DIDN'T learn in junior high...about clouds

Over a year ago, I jotted down my thoughts on making decisions about 'cloud' solutions.

While I referred to NIST (Link to NIST's definition), I thought it would be useful to offer a simple model that you might use for discussions with your colleagues, boss, or boss's boss.  Plus, it may help identify opportunities for further investigation and use.

For simplicity, you can describe 'clouds' with three main questions:

• What's special about it?  Characteristics that differentiate cloud services from traditional services.
• Where is it?  The location of the control, the actual systems, etc,
• How 'tall' is it? What components are provided?

What's Special About It?

Mainly, flexibility and adaptability.  'Cloud' architectures are focused on the ability to quickly morph to the needs of the users and owners.  Examples include:

• Access: Use the services from any device, and any network, at any time
• Scale: Quickly and effectively add more functions, users, computing power, storage, etc.
• Functionality: Acquire as individual pieces, pre-assembled components, or complete solutions.
  NOTE: The section on "How 'tall' is it?" will describe this further.

Where is It?

Many people immediately picture something that is 'out there' - out of my facilities, out of my control...  As a result, they quickly dismiss it, and miss the benefits.  In fact, there are three general 'locations':

• Private: I own it. Fully owned and controlled for a single entity / business.
• Public:  I rent it. Another firm owns and controls it, and let others use it, typically for a fee.
• Hybrid: Integration of owned and rented.  The private components are blended with public components to deliver the full, flexible service.

How Tall is It?

This is probably the most complex part...

• Software as a Service: Ready to useAn all inclusive service.  The free e-mail services are good examples. They provide the e-mail software, underlying and connected functions, as well as the supporting hardware. All you need is a device, and enough network connectivity to reach it.
• Platform as a Service: Some Assembly RequiredProvides one or more pre-assembled components that can be used to create a service.  An example would be a 'database as a service'. The service provider delivers a fully functioning database, including the necessary storage, computing, and database software. However, additional components and integration is typically required to create the entire solution.
• Infrastructure as a Service: Do it YourselfDelivers Individual infrastructure components, typically computing or storage. In this model, other infrastructure, software, and integration is needed to 'assemble' the full solution.

While the full journey will include variations on these themes, complex issues, and tough decisions, this should prepare you to start.

What are your suggestions for starting a 'Cloud' journey?