HOW TO RUN ON THREE CLOUDS AT ONCE, AND WHEN NOT TO (45 MINUTE PRESENTATION)

Summary from the TLDR Data newsletter

Form3 runs its payment platform active-active-active across AWS, Google Cloud, and Azure, treating each provider like an availability zone. Kubernetes, NATS JetStream, and CockroachDB span all three clouds, while custom DNS, networking, and disruption controls preserve quorum. Its US deployment deliberately uses active-standby instead, showing resilience architecture should follow regulatory needs, latency limits, and cost.