How to Migrate a MySQL Database to Vitess
Talkat KubeCon + CloudNativeCon North America 2019 · on Tuesday, 2019-11-19· at 11:50· Room 6D - San Diego Convention Center, Upper Level·
summary
Stepwise canary migration routes a small percentage of production traffic to VTGate stateless proxy which speaks MySQL and adds about a millisecond or two per query, letting teams validate compatibility and latency before full cutover. Data moves with an online copy called table migration (vertical split clone) that pauses only for a short final switch, can be rolled back, and later enables adding managed tablets and shards; change data capture and sync use VReplication for CDC. UTF‑8 is recommended; aim for ~250GB shards.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:03Key Adopters
- 3:25Architecture
- 10:47Migration Plan (Stage 1)
- 14:08Canary Deployment
- 15:54Phase 2: Prerequisite
- 16:30Phase 2: Add a New Tablet
- 16:45Phase 2: Table Migration
- 18:45Phase 2: Completion
related talks
30mCodename VIFL - How to Migrate MySQL Database Clusters to Vitess
41mScaling Databases with Vitess
44mIntro: Vitess
40mVitess: Introduction And New Features
42mVitess VReplication: Standing on the Shoulders of a MySQL Giant
34mInside Vitess: Building Resilient, Distributed Databases
38mIntro: Vitess
44mIntro: Vitess