Back to Devoured - September 17, 2026
DEVOURED
How To Run on Three Clouds at Once, and When Not To (45 minute presentation)

How To Run on Three Clouds at Once, and When Not To (45 minute presentation)

Data cloudinfrastructurekubernetes InfoQ
Form3 achieves triple-cloud resilience by treating AWS, Google Cloud, and Azure as availability zones, using CockroachDB and NATS for global data consistency.
What: Form3 maintains active-active-active platform availability across three clouds using Kubernetes, custom cross-cluster pod disruption budgets (X-PDB), and DNS-based routing to allow pods to communicate across provider boundaries.
Why it matters: It validates that multi-cloud architecture is viable when treating providers as fungible infrastructure units, provided you avoid cloud-specific services and invest heavily in a dedicated platform engineering team.
Takeaway: Avoid cloud-specific services like RDS or SQS if your compliance or resilience requirements mandate a multi-cloud exit strategy; choose vendor-neutral technologies like CockroachDB and NATS from the start.
Deep dive
  • Abstraction Level: Use cloud-agnostic primitives (Kubernetes, CockroachDB, NATS) to avoid maintaining separate codebases for each provider.
  • Networking: Implement cross-cloud networking using private links and custom DNS rewrites that inject the cloud provider name into address resolutions.
  • Resilience Strategy: Utilize X-PDBs (Cross-Cluster Pod Disruption Budgets) to prevent Kubernetes from taking down pods across multiple clouds simultaneously.
  • Operational Scaling: Build custom operators (e.g., Cluster Lifecycle Operator) to manage node pool updates across clouds via a single interface rather than hundreds of manual PRs.
  • Regulatory Reality: Architect resilience based on specific market expectations; active-standby may be more acceptable than active-active depending on local regulatory and latency requirements.
Decoder
  • NATS JetStream: A high-performance, distributed messaging and streaming system that supports multi-node deployment across different cloud regions.
  • Active-Active-Active: A deployment model where the application runs simultaneously on three platforms, with all platforms actively serving traffic and sharing the workload.
Original article

Full article content is not available for inline reading.

Read the original article →

Explore all 60 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi