Got this in a newsletter from Ping Identity Corporation (pingidentity.com) the other day and it made me think.
“A few weeks ago, we held one of our quarterly customer advisory meetings in our South East and Mid-Atlantic region in the U.S. These meetings always provide insight into the evolution at our large enterprise customers. Here are some of the themes that emerged:
“Cloud” is defined as anything hosted (SaaS, PaaS, IaaS, BPO, ASP) and the flood gates are opening.
Enterprises want a loosely coupled architecture, or in other words, no single vendor and integration is a key requirement.
Really, I thought? If Cloud is defined that way, why have another term? Why don’t we just keep hosted and save everyone the trouble of spring cleaning our memories? Out with one term and in with another!
I am not sure if this statement was simple reporting from what Ping discovered from their users or if it’s an attempt to make a definition. If it’s the former, I can understand well enough because at the point of paradigm change we always see a degeneration of terminology into mush. The new term is adopted to cover the old paradigm long enough for everyone to jump into a lifeboat headed in the general direction of the new idea. If that’s it, then that’s that.
But I get queasy when I think that some people in positions of decision-making authority might actually believe it. I don’t know about BPO as an idea but ASP is a retread from the Clinton administration and I thought it died when USi failed to secure customers.
Cloud is important and it shouldn’t be trivialized or homogenized into something that’s just like everything else. The reminds me of 8 year-old soccer leagues where everyone gets a trophy for showing up. But we’re all big people now (mostly) and this ain’t that.
Cloud is a new way of computing that accesses resources from the Internet or “Cloud” and creates orders of magnitude better economies for users. It is a necessary component of ubiquitous computing. Many, many companies can’t do cloud or Cloud yet and, using the lifeboat analogy, they’re jumping in with what they have.
You can imitate Clouds and many vendors are doing this but imperfectly. Think of the IT maxim — “Better, faster, cheaper, pick two” — and you’ll have an idea of what’s happening with vendors offering one or two components of Cloud Computing.
To be clear, you need IaaS, PaaS and SaaS to do cloud computing and they all need to work together for the same reason you need hardware and software. But even more importantly, this trio provides benefits equivalent to 1+1+1=4. The four comes not from loosely coupled architecture but from tight coupling because tight coupling makes it possible for users to load and go without the traditional issues of integration.
Loose coupling is not a customer benefit as I see it, it is a vendor benefit. The coupling issue is causing heartburn for some people who make their livings making independent point solutions and performing integrations. Tight coupling makes their business models less viable. But they, too, will jump on a lifeboat and figure out how to play in a tightly coupled world and many already have.
The one positive that comes out of all this is that if paradigm change drives terminology debasement, then I would say we’re about half way through the process.