The term supercloud is relatively new, but the concepts behind it have been bubbling for years. Early last decade when NIST put forth its original definition of cloud computing, it said services had to be accessible over a public network…essentially cutting the on-prem crowd out of the conversation. A guy named Chuck Hollis, a CTO at EMC and prolific blogger objected to that criterion and laid out his vision for what he termed a private cloud. In that post he showed a workload running both on premises and in a public cloud, sharing the underlying resources in an automated and seamless manner – what later became more broadly known as hybrid cloud.

That vision, as we now know, really never materialized and we were left with multi-cloud…sets of largely incompatible and disconnected cloud services running in separate silos. The point is, what Hollis put forth – i.e. the ability to abstract underlying infrastructure complexity and run workloads across multiple heterogeneous estates with an identical experience – is what supercloud is all about.