This document discusses different approaches to hybrid cloud architectures and how to get them right the first time. It outlines emerging hybrid cloud architectural patterns like static placement, assisted replication, auto migration, and dynamic migration. It emphasizes the need for cloud abstraction and defines common interfaces, services, processes, and models. It also notes that security, governance, and testing are critical to the success of any hybrid cloud architecture.
8. Current Patterns: Primitive Hybrid Architectures Public Cloud Private Cloud API/Services Migration Interoperability Public Cloud Private Cloud
9. Best: Cloud Abstraction Private Cloud B Public Cloud C Private Cloud A Abstraction Layer (Composite)
10.
11. Static Placement Bind to Platform - Difficult or impossible to dynamically port or migrate. - Little or no use of standards. - Typically older platforms mixed with cloud platforms. - Little use of abstraction. Public Cloud Data Data Private Cloud Internet Data Data Services/API
12. Assisted Replication - Code port and/or interface compatibility. - Some use of standards. - Typically new platforms that are code/service compatible. - Limited use of abstraction. Public Cloud Data Data Private Cloud Internet Data Data Services/API
13. Auto Migration - Auto code/VM migration and/or interface compatibility. - Some use of standards. - Virtualization, code, and data levels. - Some use of abstraction. Public Cloud Data Data Private Cloud Internet Data Data Services/API
14. Dynamic Migration Public Cloud Data Data Private Cloud Internet Data Data Services/API - Dynamic VM migration within single logical OS. - Logical and physical abstraction. - Some use of standards. - Hybrid cloud operating systems. OS