解锁动态页面：Netflix的客户端-服务器GraphQL API的演变
[
[
By Sreekanth Ramakrishnan, David Shin, Mehmet Yilmaz
由 Sreekanth Ramakrishnan, David Shin, Mehmet Yilmaz 提供
When a user opens the Netflix app, a flurry of activity happens behind the scenes. The app requests the homepage from a server, which assembles a personalized page using a combination of business rules, computations, and machine learning models.
当用户打开Netflix应用时，后台会发生一系列活动。该应用从服务器请求主页，服务器使用商业规则、计算和机器学习模型的组合来组装个性化页面。
Press enter or click to view image in full size
按回车键或点击以查看完整图像
Figure 1. Device and server activity behind the scenes
图 1. 设备和服务器的后台活动
In the past, once the homepage was constructed, it would remain static and unchanged for the remainder of that user’s session, with some notable exceptions such as My List and Continue Watching. A few years ago, we began experimenting with making the experience more personalized for that precise moment in time, and we updated the page dynamically based on the user’s behavior during that session. For example, after viewing multiple comedy show trailers, a user would see an updated page that included relevant comedy titles.
过去，一旦主页构建完成，它将在该用户会话的剩余时间内保持静态和不变，只有一些显著的例外，如我的列表和继续观看。几年前，我们开始尝试使体验在那个特定时刻更加个性化，并根据用户在该会话中的行为动态更新页面。例如，在观看多个喜剧节目预告片后，用户会看到一个更新的页面，其中包含相关的喜剧标题。
Enabling this experience required modifications to device call patterns, APIs, and backend page construction systems. However, as these changes were limited in nature, our systems were still largely operating with a static page paradigm. This imposed significant constraints on the nature and scope of page updates possible. To support more dynamic pages, our systems required much larger foundational investments.
启用这种体验需要对设备调用模式、API和后端页面构建系统进行修改。然而，由于这些变化的性质有限，我们的系统仍然在很大程度上以静态页面范式运作。这对页面更新的性质和范围施加了重大限制。为了支持更动态的页面，我们的系统需要更大的基础投资。
Since then, driven by evolving business needs, ...