Private cloud is not dead, hybrid cloud is a confusing term, and multi-cloud is real.
In the later half of 2016, we saw several surveys (e.g., from RightScale and InteropITX) that indicated “hybrid” and public cloud adoption were gaining at the expense of “private cloud.” It turns out enterprises are still running workloads in private clouds and will continue to do so. However, private clouds will suffer because many companies are not planning for significant new capital investments to support on-premises infrastructure.
Market confusion about “hybrid cloud’s” definition masks the dynamics of cloud adoption. Most forward-looking observers differentiate between multi-cloud and hybrid. Using a private and public cloud is multi-cloud because the enterprise is using multiple clouds at the same time. We like Carl Lehman and 451 Research‘s definition of hybrid cloud as referring to situations when a single business function is delivered across multiple clouds. Thus, when RightScale reported 67 percent using a hybrid cloud, that should have been called multi-cloud because it was based on respondents that simultaneously replied that they were “using public cloud” and using “private cloud.”
In other studies, we believe the stated preference for “hybrid cloud” actually refers to multi-cloud architectures that allow for cloud bursting or migrating an application to a different cloud to save money.
An early 2017 survey by 451 Research and Microsoft indicates that only 15 percent expect to primarily use this more robust definition of hybrid cloud. Another 53% plan on using multiple clouds. However, among that group more than half do not expect to even be able to migrate workloads between their clouds.
We also noticed that some of the studies showing large drops in “private cloud” dealt with preferences for future cloud development and not the actual percentage of current workloads being managed. 451 Research and Microsoft have actually provided a gold mine of publicly available reports based on large and global (>1,700 respondents) samples over the last several years.
Using their data, we found that hosted private cloud adoption actually increased from 61 percent in 2016 to 64 percent in 2017. Of course, IaaS usage accelerated more, going from 51 percent to 63 percent.
The aforementioned InteropITX report found that private cloud adoption declined from 2014 to 2016. However, that is based on a question that conflated virtualization with private cloud. In the report, Joe Emison noted, “2016 seemed to mark the last point in time when IT professionals could describe a collection of virtual machines” as doing cloud. That is probably hyperbole. Instead, we have seen a trend where on-premises data centers are described as the private component of hybrid clouds.
Most organizations are already well on their way to consolidating their infrastructure to virtualized environments and private clouds. Consequently, in the 2017 RightScale survey, the percentage of enterprise IT respondents focusing on building (new) private clouds dropped from 23 to 9 percent since the 2016 survey, while those leveraging their private clouds in conjunction with public clouds rose from 39 to 50 percent.
- In the short-term, we see constrained demand for new hardware- or software-based hyperconverged infrastructure that could build the next generation of private clouds hosted at enterprise data centers. While the movement to public cloud will continue, the migration of workloads to the public cloud is a slow process, with some applications actually being moved back to internal data centers.
- The use of containers within continuous integration and deployment systems now make it much easier to make a decision about migrating workloads. Application portability enables multi-cloud adoption, often times using a “lift-and-shift” approach. However, technical integration issues, including persistent storage and security, inhibit migration of many apps.
- True hybrid cloud means a single business function is delivered across multiple clouds. In these cases, infrastructure services are running on different clouds and require integration. Hybrid cloud’s need for infrastructure services interoperability is a reason why the Kubernetes Cluster Federation Special Interest Group has gained attention. This, plus efforts to popularize Cloud Foundry’s Open Service Broker API means that the components of an application will be less likely to prevent or slow down the migration of workloads.
Cloud Foundry is a sponsor of The New Stack.
Feature image via PublicDomainPictures.net.