How Geo-Distributed Apps Use Global Cloud Infra for Speed and Compliance
summary
Shows concrete multi-region options using Yugabyte: multi-region cluster, read replicas, multiple standalone clusters and a geo-partitioned cluster with tradeoffs. Gives latencies (5 ms within a region, ~98 ms transatlantic, ~270 ms to Mumbai) and a demo where reads hit a local read replica and run roughly 20x faster versus reading the U.S. primary; writes still incur cross-region roundtrips for ID allocation and replication, and deployment choice depends on whether reads alone or reads+writes and data residency are required.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:23Your Speaker: Denis Magda
- 7:30Global Cloud Infrastructure: Regions
- 10:41Possibilities With the Global Cloud Infrastructure
- 13:29Geo-Distributed Applications
- 14:11Geo-Distributed Apps: Typical Architecture
- 19:33Widespread Types of Multi-Region Database Deployments
- 20:32yugabyteDB Open Source Distributed SQL Database
- 21:37YugabyteDB: a Closer Look Into the SQL Engine
- 22:25Single Multi-Region Database Cluster
- 24:23Single Multi-Region Cluster With Read Replicas
- 26:05Multiple Standalone Database Clusters
- 28:06Single Geo-Partitioned Database Clusters
- 35:06What Database Deployment Type You Need?
- 36:17Another important takeaway...
related talks
39mHow Geo-Distributed Apps Use Global Cloud Infra for Speed and Compliance
31mToo Far Too Furious: Multi-Region Cloud Applications
01h 41mMastering Multi-Region Deployments With YugabyteDB
30mSolving Multi-Region Data Read and Write Challenges in Cross-Border Payments
44mToo Far, Too Furious: Multi-Region Spring Cloud Applications
26mA Winning Multi Cloud Data Strategy
50mWeathering the Cloud Storm: Building Resilient Geo-Distributed Apps
08mScalable GraphQL Applications Powered by Cloud-ready Distributed SQL Database
