When the Clouds Are 'Out'
It didn’t start with cloud computing--it began with the problem that there are certain products or services we need, can’t do without and have a crisis should they suddenly become unavailable. In any given organization’s history, there has been a time (even if in a small way) where they were dependent upon some component. When it became abruptly inaccessible, they put their collective heads in their hands and wondered how they were going to deal with the fallout (let alone get things going again).
Having this reliance, regardless of what it is, is often central to your operation. Sometimes, it is due to financial necessity--the need to take on the risk so as to maximize profit and minimize expenditures, but with the understanding (i. e., head-in-the-sand acceptance) that everything could fall apart catastrophically. Other times, it feels as if we have no choice--either there is no other product/service like it, or we have an investment in the component that cannot be backed away from without consequences. When we can, we treat our dependencies much like an investment model--diversifying our application portfolios so that risk is mitigated. But we’re not often that fortunate.
Now we’re entering the era of cloud computing--and somehow we’re supposed to feel better.
Same Old, Same Old
“Cloud” sounds kind of ethereal,
Please log in or sign up below to read the rest of the article.