How a Cloud is formed?

There are many misconceptions about the term cloud, usually because there are so many definitions of it. One common misconception is that clouds are completely based on virtualization. Though virtualization usually plays a major role in a cloud deployment, a cloud can also just mean a shared infrastructure. 

Take, for example, Google’s Gmail. This is public cloud service that does not rely much on virtualization. Instead, massive amounts of physical hardware are in use behind the scenes. 

The cloud is also not about having a dedicated network attached storage (NAS) hardware or server in residence. Storing data on a home or office network does not count as utilizing the cloud. For it to be considered "cloud computing," you need to access your data or your programs over the Internet, or at the very least, have that data synced with other information over the Web. 

In a big business, you may know all there is to know about what's on the other side of the connection; as an individual user, you may never have any idea what kind of massive data processing is happening on the other end. The end result is the same: with an online connection, cloud computing can be done anywhere, anytime.

Some Clouds involve a distinct and secured environment in which only the specified people can operate. So in that way, it becomes private to such people. And hence this kind of cloud is called as private cloud. Whereas a public cloud is one based on the standard cloud computing model, in which a service provider makes resources, such as virtual machines (VMs), applications or storage, available to the general public over the internet. Public cloud services may be free or offered on a pay-per-usage model.

Guess what the figure below depicts!!

Harsh but true!

Expect the journey to the cloud to have less technological challenges and more people challenges, as processes are torn down and recreated, routine tasks automated, and standardization championed. An IT department that is heavy-handed and unresponsive to users’ needs may not be in the right place to start rethinking themselves and their work. Similarly, an IT department that is overworked may not have enough free time to pursue cloud solutions, despite the time savings the cloud would provide.