Hybrid Cloud Architecture
Hybrid cloud architecture connects on-premises or private infrastructure with public cloud services. It defines where workloads run and how networking, identity, data, operations, and recovery work across the boundary.
itCloud computing | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Hybrid Cloud Architecture
Hybrid cloud architecture connects distinct computing environments. Most often, it joins on-premises or private infrastructure to public cloud services. The useful question is not which provider appears in a diagram. It is where each component belongs and what must work across the boundary.
NIST defines a hybrid cloud as two or more distinct cloud infrastructures that remain unique entities but are bound by technology enabling data and application portability. In day-to-day architecture work, the term commonly includes connected on-premises systems. Treat the connection as a real boundary. It has latency, failure modes, ownership, and security consequences.
Start with placement
Start with a workload inventory. For every component, record its users, data classification, latency target, dependencies, recovery objective, operational owner, and required interfaces. Then choose placement.
A tiered design can keep a local data-producing system near devices while an application tier runs in the cloud. An edge design can process time-sensitive events locally and send selected results onward. A business-continuity design can keep a recovery path in another environment. A migration design can move components in stages while dependencies remain where they are.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://csrc.nist.gov/pubs/sp/800/145/final
Supports
- Cloud computing has defined service and deployment models
- Hybrid cloud composes distinct cloud infrastructures that remain unique entities and are bound for data and application portability
- https://www.nist.gov/publications/nist-cloud-computing-reference-architecture
Supports
- The NIST Cloud Computing Reference Architecture provides a framework and taxonomy for cloud components and offerings
- Cloud architecture needs common terminology for components and management concerns
- https://docs.aws.amazon.com/prescriptive-guidance/latest/hybrid-cloud-best-practices/introduction.html
Supports
- Hybrid architectures can address migration, local processing, data-transfer, regulatory, and continuity requirements
- A hybrid strategy governs resource use while a technical strategy defines tenets and an implementation framework
- Consistent interfaces for provisioning and management are a hybrid architecture requirement
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/hybrid/strategy
Supports
- Hybrid cloud combines on-premises or private infrastructure and public cloud services
- Unified hybrid operations seek consistent practices across distributed environments
- https://learn.microsoft.com/en-us/azure/networking/hybrid-connectivity/hybrid-connectivity
Supports
- Hybrid connectivity is a critical component of architectures spanning on-premises, private, and public cloud services
- Connectivity selection depends on bandwidth, latency, and resiliency requirements
- https://docs.cloud.google.com/architecture/hybrid-multicloud-patterns-and-practices?hl=en
Supports
- Hybrid and multicloud patterns are tailored to workload requirements and constraints
- Common patterns include distributed tiered and edge patterns plus redundant business-continuity and cloud-bursting patterns
- Architecture patterns define components, functions, and communication among components