Form3's Multi-Cloud Journey: Lessons from the Trenches

Navigating the Multi-Cloud Minefield

The Form3 case study presented at QCon London 2026 offers a refreshingly candid look at the realities of implementing a triple-active multi-cloud architecture. The key takeaway is that while technically feasible, this approach is fraught with complexity and not universally applicable. The article highlights the critical role of cloud-agnostic technologies like NATS JetStream and CockroachDB in enabling such a setup. The engineering challenges, particularly around bootstrapping distributed databases across independent Kubernetes clusters and managing cross-cloud disruption budgets, underscore the significant platform engineering investment required. The 'DNS hack' for CockroachDB and the custom XPDB operator are prime examples of the intricate solutions needed to overcome inherent multi-cloud limitations. This deep dive into the 'how' and 'why' of their UK operations provides immense value for organizations contemplating similar strategies, especially those facing regulatory pressure for cloud diversification.

However, the article's subsequent discussion on their US market expansion reveals the crucial caveat: market and customer expectations often dictate a more pragmatic approach. The realization that a triple-active setup was unsuitable due to latency constraints and unfamiliarity with the concept among US customers is a vital lesson. Form3's pivot to an active-standby architecture demonstrates that 'one size does not fit all' in cloud strategy. This highlights a broader concern: the potential for over-engineering solutions based on perceived risks (like cloud concentration) rather than concrete business or technical needs. The cost and operational overhead of a triple-active setup are substantial, and as the article wisely points out, 'bankruptcy is kind of incompatible with uptime.' The article effectively balances the 'how-to' with the 'when-not-to,' making it a valuable resource for architects and decision-makers evaluating their cloud strategies.

Key Points

• Form3 implemented a triple-active multi-cloud architecture across AWS, GCP, and Azure to address UK banking regulator concerns about cloud concentration risk.
• Key technologies enabling this included cloud-agnostic choices like NATS JetStream for messaging and CockroachDB for distributed data storage, running on independent Kubernetes clusters.
• Significant engineering challenges involved bootstrapping distributed databases, managing cross-cloud disruption budgets (e.g., XPDB operator), and simplifying cluster lifecycle management.
• The triple-active approach proved successful in the UK but was unsuitable for the US market due to latency constraints and different customer expectations, leading to an active-standby architecture.
• The article emphasizes that multi-cloud success hinges on cloud-agnostic tech, single logical data stores, treating clouds as availability zones, and having a strong platform engineering team; it's not for every market or budget.

---

📖 Source: QCon London 2026: How To Run on Three Clouds at Once, and When Not To