Understanding the concept of a hybrid cloud is easier if you first understand the key differences between public and private cloud services.
A public cloud is a virtual network of servers and services, exposed as compute resources, storage, and service APIs, which can be invoked by applications running within a publicly accessible virtual server environment. Azure and AWS are popular examples. All the servers in the public cloud exist in the same network environment, managed by the cloud provider, and applications access services using access control systems and encrypted network protocols. This simple and flexible model works for many typical cloud applications scenarios.
But if an organization wants to take the step to add additional security and to manage your own cloud network, with control just like in the on-premises datacenter, you are looking at a private cloud. A private cloud consists of a secured virtual server environment with fine levels of access control over the network architecture. A private cloud could be as simple as a single server running a few virtual compute resources, or as a virtual private cloud deployed through a public cloud provider. Private clouds on premises must implement their own virtualization software, known as a hypervisor, like VMware, which manage the virtual compute resources.
A hybrid cloud, as you might be figuring out by now, is when a public cloud and private cloud is networked together into a single, virtual environment connected via WAN. For many large, mature IT organizations, running a hybrid cloud architecture is necessary due to the sheer amount of existing infrastructure and investment already in place.
Additionally, a public cloud-compatible management layer can allow administrators to manage compute and storage resources across both public and private clouds seamlessly, giving them greater flexibility to manage security and costs. OpenStack is a popular example of this orchestration software layer.
It’s important to note that hybrid clouds can have a higher level of technical complexity than a public cloud, and often require significant expertise, particularly due to the complexity of implementing private clouds.
Why Hybrid Cloud
There are number of reasons to move to a hybrid cloud. As we’ve seen above, sometimes it’s often the only reasonable solution in the near term, as the cost, time and complexity of a full replatforming may be too much for many organizations. But there are other, often strategic reasons to use a hybrid cloud infrastructure.
Hybrid clouds are often useful when creating a seamless extension of on-premises datacenter. This facilitates the migration of applications to the cloud over time, while retaining the mature security infrastructure and processes often developed over many years. Organizations who take this approach often are selectively choosing whether to move applications to cloud or replace them with cloud-native solutions over a long period of time.
Another big reason reason is cost. On-premises computing power is often significantly cheaper than cloud computing resources, particularly for intensive uses like graphics rendering, real-time transactions, and intensive data and analytics. Expensive tasks can be handled in the datacenter with cheap, powerful, fast servers and commodity storage with high scale business applications can be handled in the cloud. This is often attractive if an organization has already made an investment in high performance computing resources.