The Case For and Against Private Clouds: Conclusion

[ Read the whole CIO.com series by Bernard Golden on private clouds. See Defining Private Clouds, Part One, Defining Private Clouds, Part Two, The Case For Private Clouds and The Case against Private Clouds. ]

My view is that private cloud is probably a better term; however, one must be careful to distinguish the implementation location, as some aspects of a private cloud hosted externally differ from an internal counterpart. For example, it's likely that a formal contract containing an SLA will be in place with an external provider of a private cloud; negotiating and enforcing that SLA will probably be different than addressing an internal SLA.

In this post I'd like to summarize the series, draw some lessons, and offer some thoughts on what steps to take as you plan a private cloud implementation.

In terms of summing up, one factor to keep in mind is the "why" of private clouds: why does it make sense to consider implementing one

The most important factor is that implementing a private cloud allows an IT organization to bypass many of the issues raised against public cloud services like Amazon EC2. First, one does not need to rely on the public cloud provider's security measures. Second, a private cloud, as mentioned just above, can provide for an SLA, whereas a public cloud may have an inadequate or non-existent SLA. Third, and quite critically, certain privacy issues that arise with public cloud use can be avoided; an example of this type of issue is the ability of the U.S. government to access an organization's data in a public cloud without the data owner knowing anything about the access. If the cloud is privately hosted, that unknown access is not an issue.