在Airbnb构建下一代Key-Value存储
[
[
Press enter or click to view image in full size
按回车或点击以全尺寸查看图片
How we completely rearchitected Mussel, our storage engine for derived data, and lessons learned from the migration from Mussel V1 to V2.
我们如何彻底重新设计了 Mussel——我们的派生数据存储引擎——以及从 Mussel V1 迁移到 V2 过程中学到的经验。
By Shravan Gaonkar, Chandramouli Rangarajan, Yanhan Zhang
作者：Shravan Gaonkar、Chandramouli Rangarajan、Yanhan Zhang
How we completely rearchitected Mussel, our storage engine for derived data, and lessons learned from the migration from Mussel V1 to V2.
我们如何彻底重新设计了 Mussel——我们的派生数据存储引擎——以及从 Mussel V1 迁移到 V2 过程中学到的经验。
Airbnb’s core key-value store, internally known as Mussel, bridges offline and online workloads, providing highly scalable bulk load capabilities combined with single-digit millisecond reads.
Airbnb 的核心键值存储，内部称为 Mussel，连接了离线和在线工作负载，提供高度可扩展的批量加载能力，并结合了毫秒级读取。
Since first writing about Mussel in a 2022 blog post, we have completely deprecated the storage backend of the original system (what we now call Mussel v1) and have replaced it with a NewSQL backend which we are referring to as Mussel v2. Mussel v2 has been running successfully in production for a year, and we wanted to share why we undertook this rearchitecture, what the challenges were, and what benefits we got from it.
自 2022 年在博客文章中首次介绍 Mussel 以来，我们已完全弃用原始系统的存储后端（现称为 Mussel v1），并用我们称之为 Mussel v2 的 NewSQL 后端取而代之。Mussel v2 已在生产环境中成功运行一年，我们想分享为何进行这次重新设计、面临的挑战以及由此带来的收益。
Why rearchitect
为何重新设计
Mussel v1 reliably supported Airbnb for years, but new requirements — real-time fraud checks, instant personalization, dynamic pricing, and massive data — demand a platform that combines real-time streaming with bulk ingestion, all while being easy to manage.
Mussel v1 多年来可靠地支持了 Airbnb，但新的需求——实时欺诈检测、即时个性化、动态定价以及海量数据——要求一个能够同时处理实时流式传输与批量摄取，并且易于管理的平台。
Key Challenges with v1
v1 的关键挑战
Mussel ...