Rethinking Tactical Cloud Computing

Much of my time over the past two weeks have been focused on the validity of a cloud computing subset generally referred to as "tactical cloud computing". Although most (including me) feel the term to be inadequate, this concept is focused around using cloud computing technologies and concepts to support short-lived virtual IT infrastructures over adhoc networks. From a practical sense, this capability could be used to provide advanced computation and storage capabilities in edge-of-network operational settings. Use cases range from medical mass casualty scenarios to naval battle fleet engagements. During the NCOIC plenary two weeks ago the Cloud Computing Working Group even identified specific tactical cloud computing traits that included:

• Limited or intermittent network connectivity;
• A network connection authorization schema;
• Redundant compute and storage processes; and
• Advanced autonomic computing capabilities.

The group was, however, clearly challenged in its attempt to select an appropriately descriptive term for this capability. Offerings included similarly unfulfilling terms like "deployable cloud computing" and "adhoc cloud computing". We also failed to develop an appropriate definition to set this apart from the more widely used "enterprise cloud computing". With all signs of progress on this matter evaporating, the discussion was tabled for a unspecified future debate.

With that issue temporarily settled, my personal weekend plans included reading an advance copy of the forthcoming Meghan-Kiffer Press title "Enterprise Cloud Computing" by Andy Mulholland, Jon Pyke and Peter Fingar. In setting the learning objectives for the book, the authors provided an excellent enterprise cloud computing FAQ that appropriately included,"What is enterprise cloud computing?":

"Enterprise cloud computing is the special case of utilizing cloud computing for competitive advantage through breakout opportunities for both cost savings and, more importantly, for business innovation in terms of unprecedented speed and agility and vastly improved collaboration with business partners and customers."

An excellent definition with which I could wholeheatedly agree. Unfortunately for me though, it got mind once again wrapped around the tactical cloud computing definition dilemma. With those thoughts chewing on me like a bad case of indigestion I moved on through the excellent prose until halfway through chapter two, when another definition and description brought me again face-to-face with my nemisis:

"Cloud Service Arbitrage: Brokers supply flexibility and "opportunistic choices" ... cloud service arbitrage will be similar to cloud service aggregation, except that the services being agregated won't be fixed."

As if struck by the strength of a super-antacid, my tactical cloud computing indigestion seemed to be cured! Not only was the concept seemingly validate by the authors, but in one fell swoop, they lit the path towards a clear and concise descriptive term and definition:

Arbitraged Cloud Computing: a special case of cloud computing in which cloud services are managed, aggregated and delivered in a variable or adhoc cloud service availability environmnet.

So is this it? Can I go back to my NCOIC colleagues with this as the final answer?

( Thank you. If you enjoyed this article, get free updates by email or RSS - KLJ )