Choosing Cloud Native Technologies for the Journey to Multi-cloud
summary
Form3 migrates payment services to managed Kubernetes on AWS, GCP and Azure, using Cilium for cross‑cloud networking, NATS JetStream as the event bus and CockroachDB with a replication factor of three to keep strong consistency. Architecture keeps per‑cloud stacks identical, uses leaf nodes/superclusters to bridge NATS clusters, achieves inter‑cloud latency of a few milliseconds, and relies on toxiproxy testing and retry‑aware design to handle increased error surface during multi‑cloud operation.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:15Choosing Cloud Native Technology for the Journey to the Multi-Cloud
- 1:39Introduction
- 2:14What Form Three Does
- 3:46Maintenance
- 7:13The Challenge of Deployment
- 7:55Kubernetes
- 10:03Multi-Cloud Stacks
- 11:25Introduction to Psyllium
- 12:51Multi-Cloud Connectivity
- 15:26Introduction to What Nats Is
- 18:45Database Storage
- 19:17What Is Cockroachdb
- 26:02How Do You Handle Private Keys and Key Sharing and Secrets across Multiple Clouds Is that Something You Have Solved
related talks
31mWhen Failure Is Not an Option: Surviving Cloud Outages in Go
24mConfluent's Multi-Cloud Journey to Cilium: Pitfalls and Lessons Learned
52mFast and Furious Multi-Cloud Connectivity
24mCloud Native Promises, On-Premises: Bump Your Load Balancing To V2 With Cilium
07mMulti Cloud Native Networking and Network Security
29mLessons Learnt Developing and Deploying a Cloud Native Network Function
14mKey strategies to simplify your application journey
39mThe State of the Cloud Native Network: Deep-dive from TAG-Network