Zero-downtime migration for billing
Led traffic replay and dual-write strategy to migrate billing to a new schema without customer impact.
3
Challenges
2
Solved
1
Part of
Impact & Results
No customer-visible impact; rollback plan rehearsed twice before launch.
The Story
How this challenge was approached and solved
Built a replay harness off Kafka to validate reads/writes against the new schema, then dual-wrote during cutover. Added idempotent handlers, versioned contracts, and Envoy traffic shaping. Monitored money-movement deltas to ensure zero drift.
Focus Areas
MigrationsResilience
Tools & Technologies
PostgresVitessGoEnvoy
Screenshots
A closer look at the work