A multicloud configuration coordinates infrastructure across multiple public cloud providers to place workloads, teams, or resources where they fit best. section 12.3.2
Use implementation practices that keep provider differences visible and manageable:
- Build a separate IaC module for each cloud provider; provider-specific modules reduce complexity, support isolated testing, and expose resource ownership. section 12.3.2
- Compare workload and time-based costs before moving services, including charges for transfers between regions, zones, networks, and clouds. section 12.3.2 section 12.3.3
- Prefer private networking where possible and consolidate communicating services when cross-region or cross-cloud transfer costs outweigh migration benefits. section 12.3.3
Moving batch processing
A reporting team shifts selected batch pipelines from Google Cloud Dataflow to Amazon EMR through a different IaC module, using blue-green deployment to reduce disruption. Azure HDInsight provides an equivalent service. section 12.3.2
Figure 12.13 The report service switches its batch-processing job to use Amazon EMR instead of Google Cloud Dataflow by referencing a different module.
Shows a report service switching its batch-processing job by referencing a different provider module. section 12.3.2
Figure 12.14 Refactor your IaC to support an integration testing environment in a single availability zone and resolve to a private IP address.
Shows integration-test resources consolidated into one availability zone and resolved through a private IP address. section 12.3.3
