Security and privacy concerns mainly drive corporates from public to private clouds without realizing the fact that building private clouds have their own set of issues. Find below a few points to consider before making the move:


  • Costs Involved: Firms need to make sure they have done their due diligence and have calculated their ROIs involved in setting up a private cloud. Private clouds are expensive especially when moving from existing public clouds setup or traditional IT servers.
  • Size: When compared to a public cloud arrangement, it has been observed that private clouds cannot reach the scale or size of public clouds.
  • Phasing out Old Hardware: While building a private cloud, the old hardware that have been part of the legacy systems is usually rendered useless since they require a lot of manual configuration with the private cloud setup and it would not be possible to deploy automation management to this legacy hardware.
  • Time frame: Since operational issues and hardware management of public clouds are managed by specialized teams but while building the on premise private cloud this responsibility falls on the internal IT team which would require a bit of time frame as well as a learning curve to be observed.
  • Resistance to Change: As mentioned before, the internal IT team might not be fully prepared for this and there would be people who’d resist from reworking and changing the older operational processes to give way for the newer setup for private clouds.
  • Integration challenges: The private cloud to be built should be built on a hybrid model wherein if required it could be connected to the public clouds. This does require a lot of effort including security provisions and configurations which enable workloads to be run anywhere.