BetterDB – 跨云和自托管的开源 Redis/Valkey 迁移工具
6 分•作者: kaliades•4 个月前
我是在 Redis 担任了一年开发工具的工程经理之后构建了这个工具，当时我目睹了在许可证变更后生态系统的分裂。<p>Redis 7.4 破坏了与 Valkey 的数据文件兼容性。去年十月，唯一被广泛使用的开源迁移工具 RIOT 被归档，没有找到替代品。而云服务商——AWS、GCP、Redis Cloud——也没有动力让迁移变得容易。如果你想在不同提供商之间迁移、切换协议，或者完全脱离托管基础设施，那么你只能靠自己了。<p>BetterDB 提供了三阶段的工作流程来解决这个问题：<p>分析 - 扫描你的键空间，并在任何迁移之前标记阻塞性不兼容问题。给出绿/黄/红的判定。<p>执行 - 使用 RedisShake 实现相同协议下的高速迁移，或者使用基于命令的方式进行跨版本和跨协议的迁移，以应对二进制传输失败的情况。<p>验证 - 键数量比较、抽样检查，以及与迁移前快照的性能基线对比。<p>支持任意方向、任意提供商。既支持独立部署，也支持集群部署。<p>docker run -p 3000:3000 betterdb/monitor<p>网站：https://betterdb.com
代码库：https://github.com/BetterDB-inc/monitor
文档：https://docs.betterdb.com
查看原文
I built this after a year at Redis as an engineering manager for their developer tools, watching the ecosystem fragment after the license change.<p>Redis 7.4 broke data file compatibility with Valkey. RIOT, the only widely-used open migration tool, was archived last October with no open replacement. And the clouds - AWS, GCP, Redis Cloud - have no incentive to make leaving easy. If you want to move between providers, switch protocols, or get off managed infrastructure entirely, you're on your own.<p>BetterDB ships a three-phase workflow to fix that:<p>Analysis - scans your keyspace and flags blocking incompatibilities before anything moves. Green/amber/red verdict.<p>Execution - RedisShake for same-protocol speed, or command-based for cross-version and cross-protocol migrations where binary transfer fails.<p>Validation - key count comparison, sample spot-check, and performance baseline comparison against pre-migration snapshots.<p>Any direction. Any provider. Standalone or cluster.<p>docker run -p 3000:3000 betterdb/monitor<p>Website: https://betterdb.com
Repo: https://github.com/BetterDB-inc/monitor
Docs: https://docs.betterdb.com