Access your Pro+ Content below.
Hyperbole shades the perceived advantages of private cloud
This article is part of the Modern Infrastructure issue of July/August 2017, Vol. 6, No. 7
As the public cloud becomes more accepted by business today, a question remains: Whatever happened to the advantages of private cloud? The private cloud was supposed to bring the type of flexibility, self-service and scalability that the public cloud delivered without relying on someone else's equipment. This promise meant companies could enjoy all the benefits of cloud computing while keeping it private and secure. There are both paid tools, such as VMware's vCloud Director, and open source offerings, such as OpenStack, designed to help your business make that journey. The problem is, very few businesses took this approach, and it's looking less likely that many others will build a private cloud. The growth of AWS and Azure didn't help private cloud adoption, but these hyperscale cloud providers didn't kill off private clouds all by themselves. Private cloud principles One of the chief benefits of a cloud is scalability. The cloud's ability to instantly accommodate demand and scale resources during a spike is based on the ...
Access this PRO+ Content for Free!
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Features in this issue
As the hyper-converged market develops, container support, more flexible pricing schemes and other enhancements come to the enterprise.
Applications that are built on serverless computing and run on microservices change the way IT uses cloud. And AWS Lambda plays a key role in the shift.
IT support requires a great deal of perfunctory tasks and communications. You'll soon be able to hand off the routine to bot-based IT help desk tools and integrations.
Columns in this issue
The private cloud promised a flexible and scalable alternative to public clouds, but in many cases, the concept fails to deliver.
Just because you don't see the server doesn't mean it's not there. Serverless frameworks are superseding containers, but is the extra abstraction worth it?