Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
In reality, customers will all have a hybrid cloud environment. Today, most organizations subscribe to some sort of public cloud service(s), whether that is for their email, HR systems, backup or virtual servers. These are in some way integrated with their existing infrastructure, minimally for authentication and user information. So technically integration of public cloud and your internal existing systems infrastructure maybe doesn’t meet the definition which is that a hybrid cloud is intregation of two or more other clouds. I think this should be expanded to include integration with legacy internal private systems infrastructure. Note the illustration of the existing systems in the diagram I provided.
There seem to be a number of types of hybrid implementations evolving. I have identifed and named these three, but this is evolving quickly and I welcome input on further definition on this topic.
- Hybrid IaaS Infrastructure. This is the implementation of IaaS hardware on the customer premise and MaaS of this infrastructure from the cloud service provider. Example: Intel Hybrid Cloud and HP CloudSystem.
- Hybrid IaaS Services. This is integrating a public cloud service (like backup) with your existing systems or your private cloud systems.
- Hybrid SaaS. This is simply combining public services with your existing sytems to create new applications and business processes. For example, using your salesforce.com data, a public web service like mapping and your internal customer billing information to create a mash-up application mapping your customer sales, customer satisfaction or other information for trending and analysis. Of course, this also enables Hybrid BaaS.
Benefits. These are the same benefits that are covered in Cloud Value Proposition. In addition, other benefits include
- maintain investment in existing systems
- applications or sensitive data can remain in your private network
- less management than a private cloud
- greater control of your systems incluing architecture, access, data location, user experience, etc., but not full control as in a private cloud
- more efficient and potentially lower cost than your existing sytems and less cost than building your own private cloud or data center
Risks/Considerations. These are the sames risks identified in Cloud Risks, In addition to
- increased complexity (over public cloud)
- increated management requirements (over public cloud)
- increaed costs (over public cloud)