This whitepaper is for historical reference only. Some content might be outdated and some links might not be available. # Hybrid architecture tenets Depending on the identified use cases for a hybrid cloud implementation, enterprises must identify one or more tenets for their hybrid cloud architecture. These are some common tenets for a hybrid cloud architecture: + **Operational consistency**: Hybrid cloud customers need operational consistency across the hybrid cloud in the form of a consistent set of interfaces and APIs for resource provisioning, monitoring and managing resources on the hybrid cloud. + **Simple to control, manage, and secure**: Hybrid cloud customers want to manage hybrid cloud resources in a simple, consistent, and secure manner, similar to what they get with [AWS APIs today](https://docs.aws.amazon.com/general/latest/gr/aws-apis.html). + **Build once, deploy anywhere**: Hybrid cloud customers want to develop once and deploy workloads to cloud, on-premises, and edge environments in an agile and consistent fashion using a common set of development and management APIs, while getting consistent performance across the environment. In essence, the hybrid infrastructure must support the workload requirements, independent of where they are deployed. + **Enterprise-class application Service Level Agreements (SLAs)**: Hybrid cloud customers need their infrastructure to be highly reliable and available, similar to what they get with [AWS today](https://aws.amazon.com/legal/service-level-agreements/). + **Existing skill sets and tools**: While deploying a hybrid cloud, customers often want to leverage organizational skill sets and tools that they have already invested in.