Leveraging a Distributed SQL Database at Tokopedia: Best Practices & Lessons Learned
summary
Tokopedia describes moving core workloads onto YugabyteDB to handle 11 million merchants and 100 million daily active users, running multi-cloud active‑active clusters with a minimum of three nodes spread across zones and a replication factor of three. Migration uses Kafka connectors to stream PostgreSQL schemas and data into YSQL/YCQL, enabling follower reads and zero downtime scaling; tradeoffs include higher write latency as replication factor increases, so careful replication tuning proves essential.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:04Felix Jonathan from Tokopedia
- 2:49Tokopedia overview
- 4:15Felix's role
- 6:02Cloud-native journey
- 8:57Microservices transition
- 10:07Why distributed SQL
- 13:04Benefits for Tokopedia
- 14:27YugabyteDB APIs
- 16:36Handling app changes
- 17:19Team benefits
- 19:48PostgreSQL to YugabyteDB
- 20:51YugabyteDB deployment
- 25:10Summary
related talks
22mMigrating from Monolithic to Cloud Native Distributed SQL Database with Zero Downtime
28mDisrupting the Status Quo with Distributed SQL to Deliver Data-Driven Solutions
25mHow Sharekhan Scaled Trading Platform with Yugabyte's Distributed SQL
26mHow to Assess Your Cloud Native Workloads for Migration to a Distributed SQL Database
08mVoices of Partnership: Real Stories, Real Impact
31mLatest Developments / Japan Business and Product Updates
13mStrategic Shift to YugabyteDB as Core Database
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience