Challenges Deploying Modern Real-Time Payment Systems on Traditional RDBMS
summary
At a large payments operator processing about 50 million transactions/day (and claiming up to 3 billion digital payments monthly and 20,000+ TPS in labs), traditional RDBMS on VMware shows 5,000 active sessions, response spikes from 150 ms to 200–300 ms, and RTOs of 30–60 minutes with manual backups. Migration to YugabyteDB yields linear horizontal scale, raft-based cross-site replication, built-in sharding, YSQL/YCQL and CDC, and reports reduced latency, automatic failover and easier cloud migration.
AI-written summary · about
chapters (6)
- 0:00Magnett and real-time payments
- 1:08RDBMS limits for real-time payments
- 3:42Current RDBMS setup
- 6:34Key RDBMS production challenges
- 7:58Why YugabyteDB chosen
- 10:06YugabyteDB benefits and future
related talks
18mTowards a Lightning Fast System: Migrating a Real-Time Payment Service to
20mPowering the Future of Payments with
28mDisrupting the Status Quo with Distributed SQL to Deliver Data-Driven Solutions
18mBuilding a Scalable, Resilient System for Real-Time Fraud Detection
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience
57mNo Downtime, No Limits
36m5 Hard-Learned Lessons from Successful Database Migration and Modernization
22mBuilding a Modern Data Foundation: A Conversation with OCBC's Head of Data Architecture
