一个真实的事件溯源案例

架构师成长系列

Posted by Jason Xue on July 26, 2020

This is the third article exploring the “event” mechanism. In the first article, “Rethinking Event-Driven Architecture,” we explained how to understand “events” themselves and common architectural paradigms. In the second article, “Microservices and Event-Driven,” we discussed event-driven microservice application scenarios, especially the currently popular serverless architecture for event microservices. This article focuses on exploring a real case implementing the “event sourcing” pattern: Netflix’s user video download scenario.

Offline Viewing Business Background

As early as 2016, Netflix’s internal team received customer feedback asking, “What if members could download and watch videos offline?” For the playback licensing team, this meant providing a new content licensing system that would allow member devices to download, store, and decrypt downloaded content for offline viewing. To do this securely required a new service to handle a complex set of yet-to-be-defined business rules, as well as new interfaces for client-server interaction. Additionally, while all existing Netflix systems were stateless, this service needed to be stateful.

In late November 2016, just 9 months after the proposal was made, the Netflix team successfully launched the new download feature, allowing all members worldwide to download and play videos on their mobile devices.

[Translation to be completed…]



Related Issues not found

Please contact @soldierxue to initialize the comment

提示 / Tip

您可以通过右上角的语言切换按钮切换中英文 / You can switch between Chinese and English using the language toggle in the top right corner

提示 / Tip

您可以通过右上角的语言切换按钮切换中英文 / You can switch between Chinese and English using the language toggle in the top right corner