This is a guest post by Gbeminiyi Abolarin, Senior Infrastructure and Reliability Engineer at Topstep, in partnership with AWS.
For a live trading platform, the cache is on the critical path, not a convenience layer. When it runs on a single self-managed node with no replica and no automatic failover, one instance failure is the difference between a normal session and an outage. This post shows how Topstep migrated roughly 53 million keys from self-managed Redis OSS to a fully managed, Multi-AZ Amazon ElastiCache for Valkey cluster. The team used RedisShake for a blue/green cutover, then completed the transition with a single Amazon Route 53 DNS change in a few seconds and no application code changes beyond a small TLS configuration update.
We cover Topstep’s starting architecture, the drivers behind the move, the migration approach, the DNS and TLS considerations that teams often overlook, and the latency and operational gains Topstep realized.