From Today to 10X: Why Groww chose
summary
Groww migrates a monolithic MySQL setup to CockroachDB to gain horizontal scaling and multi-region writes while keeping existing Spring Boot/JPA apps mostly unchanged. Evaluation replays production traffic at 3x–5x amplification, injects node failures and upgrades, and verifies P95 latency stays acceptable. Migration uses CDC and bidirectional replication for zero-downtime migrations and quick rollback; five to six services are already live on CockroachDB. The move supports 50 million customers and delivers elastic scaling, with migration-tool rough edges resolved during rollout.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:38Grow’s mission and growth
- 2:45Architectural foundations and scaling
- 5:15Future scale and architecture needs
- 7:05Multi-region sharding and data locality
- 8:13Database requirements for next-gen
- 10:00Why CockroachDB selected
- 12:09Evaluation process and migration tools
- 13:53Evaluation results and challenges
- 15:18Current migration status
- 15:58Recommendations for scaling
- 17:47Q&A
related talks
14mBuilding CockroachDB for performance at scale
15mScaling to support America’s #1 sportsbook
15mScaling to support America’s #1 sportsbook
48mBuilding mission-critical applications with CockroachDB
27mBeyond the Roadmap and Into the Future of CockroachDB
31mFuture-proofing operational data at scale
23mWhy Squarespace adopted CockroachDB for better global performance at scale
15mJourney from PostgreSQL to CockroachDB: Scaling Cisco AI Defense