How Groww Migrated from MySQL to CockroachDB to Power Its Cell-Based Architecture (Part 1) Modern applications demand more than just basic database functionality. To handle massive scale and ensure …

The Groww Engineering Blog offers insights, case studies, and technical articles on building scalable and reliable financial technology platforms. Covering topics such as backend architecture, microservices, and fintech innovations, the Groww Engineering Blog provides resources for software engineers and fintech professionals seeking to build robust and secure financial products and services.

Groww Engineering

Groww, a financial platform, migrated from MySQL to CockroachDB to support a cell-based architecture capable of 10x scale. MySQL's lack of native sharding and multi-cloud failover paths drove the decision. CockroachDB was chosen for its PostgreSQL compatibility, full ACID compliance, multi-region active-active deployment (RPO=0, RTO<10s), and its 'Regional By Row' feature that enables moving users between cells by updating a single column. Key migration challenges included eliminating auto-increment IDs (replaced with UUIDs or cached sequences), fixing sequential index hotspots using hash-sharded indexes, and handling nullable column indexes with partial indexes. An automated pipeline was built to move data with minimal downtime. Part 2 will cover multi-region node deployment and cell-to-region mapping.

How Groww Migrated from MySQL to CockroachDB to Power Its Cell-Based Architecture (Part 1)

Limitations of the Previous MySQL-Based Architecture

Key Challenges: Achieving Distributed SQL Readiness

Get Groww Engineering Team ’s stories in your inbox