Too Far Too Furious: Multi-Region Cloud Applications
summary
Demo builds a small pizza microservices system (Kitchen + Tracker, Docker Compose locally, REST APIs) and deploys it to Google Cloud VMs in US East, Frankfurt and Sydney. Backend uses Postgres-compatible YugabyteDB with replication factor 3 and async read replicas and a nine-node YugabyteDB geopartition cluster. Measured latencies: US reads ~4 ms, cross-Atlantic reads ~191 ms until read replicas drop them to ~3–4 ms; geopartition achieves ~7–9 ms for local reads and writes globally. All demos succeed.
AI-written summary · about
chapters (13)
- 0:00Introduction to multi-region apps
- 1:03Why build multi-region applications
- 4:14Sample pizza company app
- 6:21Developer prototype demo
- 10:35Deploying to cloud regions
- 13:06Distributed database setup
- 15:53Baseline latency results
- 16:15Read latency issues in Europe
- 18:49Read replicas for Europe and Australia
- 22:54Optimizing write latency globally
- 23:15Geo-partitioned database cluster
- 26:50Geo-partition latency results
- 30:08Key takeaways and summary
related talks
44mToo Far, Too Furious: Multi-Region Spring Cloud Applications
38mHow Geo-Distributed Apps Use Global Cloud Infra for Speed and Compliance
39mHow Geo-Distributed Apps Use Global Cloud Infra for Speed and Compliance
01h 41mMastering Multi-Region Deployments With YugabyteDB
50mWeathering the Cloud Storm: Building Resilient Geo-Distributed Apps
26mA Winning Multi Cloud Data Strategy
31mAn Adventure in Multi Cloud with Kubernetes and Distributed Data
25mDiscover the Easiest Path to Distributed DBaaS: Yugabyte Cloud