How Sharekhan Scaled Trading Platform with Yugabyte's Distributed SQL
summary
Shares a migration from a monolithic OMS/RMS to a modular monolithic distributed design using an event-driven pipeline and Kafka-based session management for low-latency handoff and spike buffering; moves the database to YugabyteDB with sharding and plans for active‑active, near‑zero downtime DR. Benchmarked at about 4,500 orders/sec (~68,000 ops/sec) on a three‑node 32‑core cluster, and reports the architecture meets throughput and resilience goals while accepting modest network latency tradeoffs.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:11Journey with YugabyteDB
- 3:45Sharing use cases in tech
- 5:31Scale and business reach
- 6:32OMS and RMS explained
- 9:00Monolithic vs distributed trade-offs
- 10:49Event-driven distributed systems
- 13:22Why Yugabyte was chosen
- 16:05Database proof of concept
- 17:29Modular monolith design
- 18:55Kafka in low-latency systems
- 21:44Distributed DB challenges
- 22:06YugabyteDB benchmarks
- 24:13Support and future outlook
related talks
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience
18mBuilding a Scalable, Resilient System for Real-Time Fraud Detection
22mMigrating from Monolithic to Cloud Native Distributed SQL Database with Zero Downtime
17mBuilding a Scalable and Performant SaaS Platform with YugabyteDB
26mLeveraging a Distributed SQL Database at Tokopedia: Best Practices & Lessons Learned
29mDelivering Always-On Financial Services with
26mHow to Assess Your Cloud Native Workloads for Migration to a Distributed SQL Database
30mBuilding Cloud Native Applications on Distributed SQL Platform