What does it take to migrate 4.2 billion records and 6+ terabytes of live order data to DynamoDB, without stopping trading for a single second?
At Bitstamp, we did exactly that. No maintenance windows. No rollback. No critical outages. But the path there was anything but smooth, the migration took four months longer than planned and generated more production incidents than we’re proud of.
We’ll walk through the architecture that made it possible: dual-write pipelines, gradual read ramp, feature flags, and a row-level discrepancy checker that caught every correctness bug before cutover. And we’ll be equally honest about what hurt: observability gaps, schema churn mid-migration, chaos testing that came too late, and why we still couldn’t eliminate the MySQL table we set out to replace.
You’ll leave with concrete lessons on:
Designing zero-downtime migrations for high-frequency transactional systems
Why resilience patterns belong in v1, not v3
What DynamoDB won’t tell you about write latency until it’s too late
If you’re planning a large-scale database migration, or want to learn from someone who just survived one, this talk is for you.
This website uses the open source AWS Community Day Template built by AWSug.nl hosted on Amazon CloudFront and Amazon S3. The website uses bootstrap and hugo.