Too Far, Too Furious: Multi-Region Spring Cloud Applications
summary
Hands-on build of a multi-region Spring Cloud application across three regions (US East / Virginia preferred, Frankfurt, Sydney) using Spring Cloud Gateway + Eureka and YugabyteDB. Measured baseline: US end-to-end ~300 ms with DB ~8–20 ms; Berlin and Sydney initially double or worse because writes synchronously replicate to the US (Australia saw ~0.5 s backend DB latency). Adding read replicas drops DB latency to ~5 ms (total ~350 ms after connection warmup). A YugabyteDB geopartition cluster delivers comparable read/write latency per region; first-connection metadata transfer still incurs warm-up cost.
AI-written summary · about
chapters (12)
- 0:00Introduction to multi-region apps
- 1:08Reasons for multi-region deployment
- 6:29Essential components overview
- 9:19Spring Cloud components explained
- 12:53Building naive multi-region app
- 18:30Demo setup and deployment
- 24:12Baseline latency measurements
- 27:24Database bottleneck analysis
- 30:15Read replica deployment demo
- 34:50Geo-partitioned cluster demo
- 38:46Summary and deployment options
- 39:27Q&A session
related talks
31mToo Far Too Furious: Multi-Region 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
30mSolving Multi-Region Data Read and Write Challenges in Cross-Border Payments
26mGetting Started with YugabyteDB Aeon (Formerly YugabyteDB Managed)
23mGaming Across Borders: Global Distributed Databases on Tencent Cloud