Etsy's MySQL move to Vitess opens new paths for data growth and flexibility.

Etsy's engineering team has successfully migrated its extensive MySQL sharding architecture, encompassing 1,000 shards and 425 TB of data, to Vitess.

3 min readInfoQ
Etsy's MySQL move to Vitess opens new paths for data growth and flexibility.

Etsy's migration from its long-standing MySQL sharding setup to Vitess is the kind of infrastructure story that rarely makes headlines but deserves them. The company didn't just swap one tool for another; it replaced a system that had reached its limits with one built to scale beyond them. For anyone managing data growth, this is a signal that the old ways of sharding are no longer the ceiling.

The practical takeaway is straightforward: Etsy's move to Vitess means shard routing now happens through vindexes, which opens doors that were previously locked. Resharding, once a painful and risky operation, becomes a capability rather than a project. Tables that were never sharded because the effort wasn't worth the payoff can now be brought into the fold. For teams running on MySQL, this isn't just a technical upgrade; it's a new set of options for how to grow without painting yourself into a corner.

What stands out is the shift in mindset. Etsy's internal routing system worked for years, but it was built for a different era of data. Vitess doesn't just automate what came before; it changes what you can consider doing at all. If you've been putting off sharding because the operational cost seemed too high, or if you've been living with a sharding scheme that's become rigid, this migration shows a path forward that doesn't require a rewrite or a leap into an entirely new database. It's a reminder that sometimes the most transformative change is the one that makes future changes possible.

For practitioners, the lesson is concrete: evaluate whether your current sharding approach is a foundation or a constraint. Etsy's experience suggests that moving to Vitess isn't just about fixing today's bottlenecks; it's about making sure you're not the team that has to say "we can't" when the next wave of data arrives. The flexibility to reshard and to shard previously untouched tables isn't a luxury; it's becoming a baseline expectation. If your data is growing, the question isn't whether you'll need that flexibility. It's whether you'll have it.

From InfoQ

The Etsy engineering team recently described how the company migrated its long-running MySQL sharding infrastructure to Vitess. The transition moved shard routing from Etsy’s internal systems to Vitess using vindexes, enabling capabilities such as resharding data and sharding previously unsharded tables.

Read the original at InfoQ