How Geo-Distributed Apps Use Global Cloud Infra for Speed and Compliance
summary
Shows concrete options for low-latency, compliant geo apps using global cloud infra and YugabyteDB as the example: claim is that multi-region design equalizes latency (5 ms within a region, ~98 ms US–Europe, ~270 ms US–Mumbai) and meets data residency (GDPR, RBI). Demonstrates a primary in US east with a read replica in Taiwan where a 42-row read drops from ~200 ms to ~10 ms (~20x), writes still route to primary (observed ~700 ms), and compares read replicas, multiple standalone clusters, and geo-partitioned cluster.
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
40mMulti-Cloud Global Content Distribution at Cloud Native Speeds
22mCloud Native GIS - The value of development velocity in GIS
32mBest Practice in Design and Implementing MySQL Geographic Distributed, High Availability Solutions- 40mMulti-Cloud Global Content Distribution at Cloud Native Speeds
41mAn Adventure in Multi-Cloud with Kubernetes
35meBay Geo-Distributed Database on Kubernetes [A]
31mAn Adventure in Multi Cloud with Kubernetes and Distributed Data
20mComposing the Cloud, 2.0