Netflix 的 Cassandra 数据移动演进

[

Netflix TechBlog

Netflix 技术博客

](https://netflixtechblog.com/?source=post_page---publication_nav-2615bd06b42e-6e13329c80a1---------------------------------------)

[

Netflix TechBlog

](https://netflixtechblog.com/?source=post_page---post_publication_sidebar-2615bd06b42e-6e13329c80a1---------------------------------------)

Learn about Netflix’s world class engineering efforts, company culture, product developments and more.

了解 Netflix 世界级的工程成果、企业文化、产品开发及更多动态。

By Guil Pires, Jennifer Prince, Jose Camacho, Ken Kurzweil, Phanindra Chunduru

作者：Guil Pires、Jennifer Prince、Jose Camacho、Ken Kurzweil、Phanindra Chunduru

Background

背景

In a previous post, we introduced Data Bridge, a unified management plane for batch Data Movement at Netflix. Historically, several bespoke Data Movement connectors were developed across different engineering organizations to fulfill their specific requirements. Over the last few years, the Data Movement team has started centralizing these offerings through an abstraction that provides a catalog of connectors, along with simple UI and APIs to initiate Data Movement jobs.

在之前的文章中，我们介绍了 Data Bridge，这是 Netflix 用于批量 Data Movement 的统一管理平面。过去，不同的工程团队为了满足各自的特定需求，开发了多个定制的 Data Movement 连接器。在过去几年里，Data Movement 团队开始通过一个抽象层来集中管理这些服务，该抽象层提供了一个连接器目录，并配备了简单的 UI 和 API 来启动 Data Movement 作业。

One such case is the Cassandra to Iceberg connector. Apache Cassandra powers mission critical applications at Netflix, including Member, Billing, Recommendations, Subscriptions and many more. These use cases heavily leverage Data Movement to Apache Iceberg for many analytics and operational tasks, and central to this movement was a connector for Cassandra to Iceberg built in-house named Casspactor. As many Cassandra based Data Abstractions emerged, such as Key ...