Solving Multi-Region Data Read and Write Challenges in Cross-Border Payments
summary
Claims that YugabyteDB replaces complex single-region RDBMS setups for cross-border payments by providing Postgres-compatible SQL, horizontal scale-out, and built-in high availability. Describes building active-active multi-region clusters (Asia, America, Europe, India) with geo-partitioning and multi-master replication so local services can write and read with low latency, satisfy data‑locality regulations, and survive node/region failures. Reports successful testing and production deployment at Airwallex with those architectures in use.
AI-written summary · about
chapters (22)
- 0:00Multi-region data challenges
- 1:04Distributed databases necessity
- 2:55RDBMS vs NoSQL/NewSQL
- 5:06Single vs multi-region requirements
- 7:13Scaling up vs out
- 9:29Distributed DB for high availability
- 12:21Choosing multi-region DB
- 13:03Everest’s global needs
- 14:50High availability in single-region
- 15:57Traditional HA limitations
- 17:00Multi-master replication
- 19:07Why multi-master replication
- 20:13Regulatory requirements like GDPR
- 22:04Multi-region reads/writes architecture
- 23:29Database-layer solutions
- 24:35YugabyteDB at Everest
- 25:39YugabyteDB deployment
- 26:21Active-active global writes
- 27:26Scaling active-active clusters
- 28:11Geography-aware storage
- 29:11Multi-region solutions summary
- 29:33Q&A
related talks
01h 41mMastering Multi-Region Deployments With YugabyteDB
38mHow Geo-Distributed Apps Use Global Cloud Infra for Speed and Compliance
08mScalable GraphQL Applications Powered by Cloud-ready Distributed SQL Database
26mA Winning Multi Cloud Data Strategy
30mTechnical Comparison of YugabyteDB with Oracle and PostgreSQL
26mHow Boltic Scales Globally: Building a Multi-Region SaaS for Millions with
25mDiscover the Easiest Path to Distributed DBaaS: Yugabyte Cloud
20mPowering the Future of Payments with