Welcome!

If everyone is thinking the same, someone isn't thinking

Lori MacVittie

Subscribe to Lori MacVittie: eMailAlertsEmail Alerts
Get Lori MacVittie via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: Cloud Computing, Cloudonomics Journal, CIO/CTO Update, Sarbanes Oxley on Ulitzer, Java in the Cloud, DevOps for Business Application Services, DevOps Journal

DevOpsJournal: Blog Feed Post

Private Cloud is not a Euphemism for Managing Hardware

#cloud #infosec #devops Private cloud is about management, but not about hardware

As with every technology, definitions almost immediately become muddled when it becomes apparent that the technology is going to "change the world." SDN is currently suffering from this risk phenomenon and it appears that cloud continues to suffer from it. Let me present Exhibit AAAA:

Which Cloud Delivery Model is Right for Your Business?

 

Private clouds are great solutions for organizations looking to keep their hardware locally managed.

The association of "private cloud" with "hardware" is misguided and, in most instances, just plain wrong. Organizations implementing or planning on implementing private cloud (or on-premise cloud) are not doing so because they can't bear to part with their hardware. What they can't bear to part with is control. Control over security, over performance, over availability. Control over data and access. Control over their own destiny.

Private cloud, assuming an organization adopts the model fully, affords IT the same benefits of a service-focused approach to resource management as does public cloud. The difference is solely in who incurs the expense of maintaining and managing the hardware. In fact, the statement above would be more properly expressed as "private clouds are great solutions for organizations in spite of keeping hardware locally managed."

It is unlikely any organization wants to continue maintaining and managing hardware. In addition to management overhead, it comes with other baggage such as heating and cooling and power costs (not to mention the liability insurance against tripping over cables in the data center). But when measured against the weight of losing control over policies (particularly those related to compliance and security) as well as access to what most would consider standard application services (acceleration, optimization, programmability, identity management), the overhead from managing hardware locally just can't win.

And no matter how ambitious, no organization with an existing data center is going to initiate a project that includes a wholesale transition to public cloud. Whether it's integration concerns, costs associated with transitioning legacy applications to a cloud-friendly architecture, or other application-related issues arising from such a transition, non green-field organizations are simply not going to wholesale pick up their toys and move to a public cloud. But that doesn't mean those organizations or its leadership is immune to recognizing and desiring the value inherent in the cloud computing model. Private cloud models can afford organizations the same benefits as public cloud minus the cost savings that come from economy of scale.

And even if private cloud can only realize half the cost savings of public cloud, so what? When measured against potential losses from unacceptable risk, that's likely quite the deal.

Private cloud is simply not a euphemism  for managing hardware any more than public cloud is a euphemism for not managing hardware. 


  F5 Networksclip_image003[5]clip_image004[5]clip_image006[5]clip_image007[5]clip_image008[5]

Read the original blog entry...

More Stories By Lori MacVittie

Lori MacVittie is responsible for education and evangelism of application services available across F5’s entire product suite. Her role includes authorship of technical materials and participation in a number of community-based forums and industry standards organizations, among other efforts. MacVittie has extensive programming experience as an application architect, as well as network and systems development and administration expertise. Prior to joining F5, MacVittie was an award-winning Senior Technology Editor at Network Computing Magazine, where she conducted product research and evaluation focused on integration with application and network architectures, and authored articles on a variety of topics aimed at IT professionals. Her most recent area of focus included SOA-related products and architectures. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University.