Multi-Cloud Architecture
Multi-cloud architecture uses services from more than one public cloud provider. It assigns workloads and shared controls to providers while accounting for cross-cloud networking, identity, data, operations, cost, and failure.
itCloud computing | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Multi-Cloud Architecture
Multi-cloud architecture uses services from more than one public cloud provider. It is a placement strategy, not a requirement to copy every workload everywhere.
The useful question is why a second provider belongs in the design. A provider may offer a required regional presence, a differentiated service, or a platform inherited through an acquisition. A separate provider may also host an independent workload. Each reason creates different architecture and operating requirements.
Google Cloud describes multi-cloud as a means to meet business and technical objectives, not a goal by itself. AWS makes the same point through workload placement guidance. Start with a named outcome. Then test whether another provider improves that outcome after you count the added complexity.
Choose a topology
There are three useful starting topologies.
Portfolio placement assigns separate workloads to separate providers. Each workload can use its provider's native services. Cross-cloud dependencies stay limited.
Partitioned application assigns distinct application components to different providers. This can satisfy a specific capability or placement constraint. It also creates cross-cloud data and network dependencies.
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://www.nist.gov/publications/nist-cloud-computing-reference-architecture-0
Supports
- The NIST Cloud Computing Reference Architecture provides a vendor-neutral taxonomy for cloud actors, service models, and management responsibilities
- A cloud architecture can separate provider, consumer, broker, auditor, and carrier responsibilities
- https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/manage/hybrid/server/best-practices/vmware-ubuntu-template
Supports
- Multi-cloud means using multiple cloud providers concurrently
- A multi-cloud strategy should align business drivers, vision, principles, metrics, and technology choices
- Common operations across environments require consistent practices and centralized visibility
- https://docs.cloud.google.com/architecture/hybrid-multicloud-patterns/drivers
Supports
- Multi-cloud architecture is a means to meet business and technical objectives rather than a goal by itself
- Placement considerations include data sovereignty, cost, provider capability, lock-in, reliability, management complexity, security, performance, and skills
- Cross-provider resilience requires assessment of data movement, capability parity, security, manageability, and team skills
- https://docs.cloud.google.com/architecture/hybrid-multicloud-patterns-and-practices?hl=en
Supports
- Architecture patterns define components, their functions, and their communication
- Distributed patterns place workloads or components in suitable environments
- Redundant patterns deploy equivalent workloads in multiple environments for capacity, resilience, development, or testing
- https://docs.cloud.google.com/architecture/hybrid-multicloud-secure-networking-patterns/design-considerations
Supports
- Cross-environment network performance includes bandwidth, latency, packet loss, and jitter
- Connectivity decisions should assess performance, security, cost, reliability, and scalability
- Multi-cloud networking needs integrated DNS and a unified security posture with visibility across environments
- https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-multicloud/introduction.html
Supports
- Legitimate reasons for and against multi-cloud require balancing business value with complexity and risk
- Multi-cloud strategy includes business alignment, governance, workload boundaries, integration, security, and team structure
- https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-multicloud/tenet-4.html
Supports
- Splitting contiguous workloads across providers adds data movement, synchronization, consistency, security, and operating complexity
- Messaging, loose coupling, bulk transfer, and operational independence can reduce cross-provider impact
- https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-multicloud/tenet-5.html
Supports
- Workload placement should consider technical requirements, business needs, and provider strengths
- Applications benefit from placement near primary data
- Data ownership, classification, transfer method, latency, cost, and operational effects belong in placement decisions
- https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-multicloud/tenet-8.html
Supports
- Multi-cloud security spans identity, data, network, endpoint, asset, and audit concerns
- A unified security operations and observability model should retain provider-native controls