从孤岛到服务拓扑：Netflix 为何构建实时服务地图

[

Netflix TechBlog

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

[

Netflix TechBlog

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

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

了解 Netflix 世界一流的工程实践、企业文化、产品开发等更多内容。

By Parth Jain, Rakesh Sukumar, Yingwu Zhao, Renzo Sanchez-Silva & Nathan Fisher*
How we built a living map of our distributed infrastructure to help engineers understand dependencies, troubleshoot faster, and keep Netflix running smoothly for our members around the world.*

作者： Parth Jain、 Rakesh Sukumar、 Yingwu Zhao、 Renzo Sanchez-Silva & Nathan Fisher*
我们如何构建分布式基础设施的实时映射，帮助工程师理解依赖关系、更快排查故障，并保障Netflix为全球会员提供顺畅的服务。*

The Puzzle with a Thousand Pieces

千片拼图

Picture this: It’s 3am, and an ==engineer== gets paged. One of our critical services is showing elevated error rates. Members trying to watch their favorite films and series are seeing degraded experiences. The clock is ticking.

想象一下：凌晨 3 点，一位 ==工程师== 收到了寻呼报警。我们的一个关键服务显示出错误率升高。试图观看他们喜爱的电影和剧集的会员们正经历着体验下降。时间正在流逝。

A central service node connected to multiple downstream services and data stores, illustrating the tangled dependency graph engineers must navigate without a service topology map.

A single service at the center of a web of dependencies — services, data stores, and call chains branching in every direction. Without a unified map, engineers have to reason about this structure from memory and scattered signals.

一个单一的服务处于依赖关系网的中心——服务、数据存储和调用链向四面八方分支。如果没有统一的地图，工程师只能依靠记忆和零散的信号来推断这种结构。

In a system with thousands of microservices supporting our entertainment experience for members worldwide, answering these questions quickly can mean the difference between a minor blip and a major incident.

在一个拥有数千个微服务、为全球会员提供娱乐体验的系统中，快速回...