Module / Topic: Multi-Cloud
Browse Mergen content
-
Webinar: Data Residency Strategy in a Multi-Region World
Data residency requirements are tightening globally. This webinar covers strategy patterns that work without doubling infrastructure cost.
-
Vendor Lock-In is Overrated — When to Pick a Stack
“Avoid vendor lock-in” is conventional wisdom. It’s also wrong about half the time. When picking a stack is the right call.
-
Global Bank: Multi-Cloud Strategy Aligned to Regulatory Requirements Across 22 Markets
A global bank’s 22-market multi-cloud strategy aligned workload placement to data-residency, concentration-risk, and regulatory-resilience rules.
-
Multi-State Health System: Multi-Cloud for Clinical-Workload Survivability
A health system architected multi-cloud (Azure primary, AWS DR) for clinical-workload survivability. 90-min RTO; 15-min RPO; quarterly drills validate readiness.
-
Global Conglomerate: Multi-Cloud Operating Model Across AWS + Azure + GCP
A global manufacturing conglomerate with operations on all three clouds built a unified multi-cloud operating model. Per-cloud sprawl down 60%; cross-cloud visibility unified.
-
The Multi-Cloud Decision Framework: When to Federate, When to Consolidate
A decision framework for multi-cloud strategy — when consolidation wins, when federation wins, and how to structure workload routing rules.
-
Global Bank: Multi-Cloud Strategy (AWS + Azure) with Workload Routing
A global bank built a multi-cloud strategy routing workloads to AWS or Azure based on regulatory and cost factors. Vendor-lock-in risk eliminated.
-
Health System: Multi-Cloud Disaster Recovery (Azure → AWS)
A health system architected multi-cloud DR with Azure as primary and AWS as DR. RTO compressed to 90 minutes; RPO under 15 minutes for critical clinical workloads.