超越 REST

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"娱乐业一直在努力应对 COVID-19 对全球制作的影响冲击。自 2020 年初以来，Netflix 一直在迭代开发系统，以向内部利益相关方和企业领导者提供有关疫情最新信息的最新工具和仪表盘。这些软件解决方案使得管理层可以就给定的实体产品是否以及何时能够安全地开始在全球范围内创建引人注目的内容而做出最明智的决策。在 Netflix Studio Engineering 内部，一种备受关注的方法是将 GraphQL 微服务（GQLMS）作为后端平台来促进应用程序的快速开发。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"许多组织都在拥抱 GraphQL，以其作为统一企业范围内数据模型的一种方式，并提供了一个用其相关实体网络来导航大量结构化数据的单一入口点。这种努力值得称赞，但往往需要内部组织之间历经几个季度的协调，然后将所有相关实体开发并集成到一个单一的单体图中。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"与“用一张图来管理所有对象”的方法不同，GQLMS 只是利用 GraphQL 来作为构建 CRUD 应用程序的丰富 API 规范。我们使用 GQLMS 进行了快速的概念验证应用，其经验证实了 GraphQL 宣传其好处时所提出两个理论："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"GraphiQLIDE 在模式（schema）旁边显示任何可用的 GraphQL 文档，从而极大地改善了 API 使用者的人机工程学（与同类中最好的 Swagger UI 相比）"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"GraphQL 的强类型系统和多语言客户端支持，意味着 API 提供者无需关心特定于语言的 API 客户端的生成、版本控制和维护（比如，那些使用优秀的 Swagger Codegen 生成的客户端）。GraphQL API 的使用者可以简单地利用自己喜欢的开源 GraphQL 客户端。"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/wechat\/images\/5c\/5cc573a3927822c6497ab3f6f67915ec.png","alt":null,"title":null,"style":null,"href":null,"fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","text":"GraphiQL：为 《星球大战》API 自动生成的测试 GUI"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"我们的经验已经为对 GQLMS 作为快速开发平台感兴趣的团队带来了一个具有许多最佳实践的架构。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/wechat\/images\/0f\/0f0153bd41407fbfa450b06aa92ff31a.png","alt":null,"title":null,"style":null,"href":null,"fromPaste":false,"pastePass":false}},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"Graphile"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在早期的 GraphQL 探索过程中，Netflix 的工程师意识到 Graphile 库可以将 PostgreSQL 数据库对象（表、视图和函数）作为 GraphQL API 来呈现。Graphile 支持 智能注解，支持通过使用特定格式的 PostgreSQL 注解标记数据库的表、视图、列和类型来控制各种特性。文档甚至可以嵌入到数据库注解中，以便在 Graphile 生成的 GraphQL 模式中显示。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"我们假设有一个 Docker 容器，其上运行了一个带有 Graphile 库的非常简单的 NodeJS Web 服务器（以及一些用于安全、日志、度量和监控的 Netflix 内部组件），可以为快速开发工作提供“比 REST 更好的 REST”或“REST++”平台。使用 Docker，我们定义了一个轻量级的独立容器，它允许我们将 Graphile 库及其支持的代码打包成一个独立的包，任何团队都可以在 Netflix 上使用它，而无需额外的编码。只需下拉定义 Docker 的基础镜像，并使用适当的数据库连接符运行它即可。这种方法被证明是非常成功的，并且对 Graphile 的使用产生了一些深刻洞察。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"具体来说："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"使用数据库视图作为“API 层”来保持灵活性，以允许在不变更现有 GraphQL 模式（构建在数据库视图上）的情况下修改表。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"使用 PostgreSQL聚合函数 时，请使用 PostgreSQL复合类型。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"通过允许 GraphQL 客户端“所用权限”（“full access”）自动生成的 GraphQL 查询和 Graphile 生成的突变（在所有表和视图上公开的 CRUD 操作）来提高灵活性；然后在开发过程的后期，删除在应用程序投产之前未被 UI 使用到的模式元素。"}]}]}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"数据库视图作为 API"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"我们决定将数据表放在一个 PostgreSQL 模式中，然后在另一个模式中定义这些表的视图，同时 Graphile Web 应用程序使用专用的 PostgreSQL 用户角色连接到数据库。这最终能实现几个不同的目标："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"可以独立于 GraphQL 模式中公开的视图来更改底层表。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"视图可以进行基本的格式化（比如将 TIMESTAMP 字段呈现为 ISO8601 字符串）。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"底层表上的所有权限必须显式地授权给 Web 应用程序的 PostgreSQL 用户，以避免意外的写操作。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"表和视图可以在同一个事务中进行修改，这样就可以原子地对公开的 GraphQL 模式进行更改。"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"关于最后一点：更改表中列的类型将会打破关联的视图，但是通过封装在事务中的更改，可以删除视图、更新该列，然后可以在提交事务之前重新创建视图。我们在启用 pgWatch 的情况下运行 Graphile，只要对数据库做任何更新，GraphQL 模式就会立即更新以反映所做的更改。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"PostgreSQL 复合类型"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Graphile 在读取 PostgreSQL 数据库模式以及将表和基本视图转换为 GraphQL 模式方面做得非常出色，但我们的经验表明，当视图中存在 PostgreSQL聚合函数 或 JSON 函数 时，Graphile 在如何描述嵌套类型方面存在局限性。原生 PostgreSQL 函数，比如"},{"type":"codeinline","content":[{"type":"text","text":"json_build_object"}]},{"type":"text","text":"，将被转换成 GraphQL"},{"type":"codeinline","content":[{"type":"text","text":"JSON"}]},{"type":"text","text":"类型，该类型只是一个"},{"type":"codeinline","content":[{"type":"text","text":"String"}]},{"type":"text","text":"，没有任何内部结构。例如，以这个返回"},{"type":"codeinline","content":[{"type":"text","text":"JSON"}]},{"type":"text","text":"对象的简单视图为例："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"codeblock","attrs":{"lang":"makefile"},"content":[{"type":"text","text":"postgres_test_db=# create view postgraphile.json_object_example as\n select json_build_object(‘hello world’::text, 1, ‘2’::text, 3)\n as json;\npostgres_test_db=# select * from postgraphile.json_object_example;\n json\n— — — — — — — — — — — — -\n{“hello world”: 1, “2”: 3}\n(1 row)\n"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在生成的模式中，数据类型为"},{"type":"codeinline","content":[{"type":"text","text":"JSON"}]},{"type":"text","text":"："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/wechat\/images\/65\/651a015c4555abc8c1bcbb321f72bb9e.png","alt":null,"title":null,"style":null,"href":null,"fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"codeinline","content":[{"type":"text","text":"json"}]},{"type":"text","text":"字段的内部结构（"},{"type":"codeinline","content":[{"type":"text","text":"hello world"}]},{"type":"text","text":"和"},{"type":"codeinline","content":[{"type":"text","text":"2"}]},{"type":"text","text":"这两个子字段）在生成的 GraphQL 模式中是不透明的。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"为了进一步描述"},{"type":"codeinline","content":[{"type":"text","text":"json"}]},{"type":"text","text":"字段的内部结构（将其在生成的模式中公开），定义一个复合类型，并创建一个返回该类型的视图："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"codeblock","attrs":{"lang":"bash"},"content":[{"type":"text","text":"postgres_test_db=# CREATE TYPE postgraphile.custom_type AS (\n \"hello world\" integer,\n \"2\" integer\n);\n"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"接下来，创建一个返回该类型的函数："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"codeblock","attrs":{"lang":"bash"},"content":[{"type":"text","text":"postgres_test_db=# CREATE FUNCTION postgraphile.custom_type(\n \"hello world\" integer,\n \"2\" integer\n)\nRETURNS postgraphile.custom_type\nAS 'select $1, $2'\nLANGUAGE SQL;\n"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"最后，创建一个返回该类型的视图："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"codeblock","attrs":{"lang":"makefile"},"content":[{"type":"text","text":"postgres_test_db=# create view postgraphile.json_object_example2 as\n select postgraphile.custom_type(1, 3)\n as json;\npostgres_test_db=# select * from postgraphile.json_object_example2;\n json\n— — — -\n(1,3)\n(1 row)\n"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"乍一看，这似乎没有什么用，但要记住：在查看生成的模式之前，请在视图、自定义类型和自定义类型的字段上定义注解，以利用 Graphile 的智能注解："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"codeblock","attrs":{"lang":"cs"},"content":[{"type":"text","text":"postgres_test_db=# comment on\n type postgraphile.custom_type\n is E’A description for the custom type’;\npostgres_test_db=# comment on\n view postgraphile.json_object_example2\n is E’A description for the view’;\npostgres_test_db=# comment on\n column postgraphile.custom_type.”hello world”\n is E’A description for hello world’;\npostgres_test_db=# comment on\n column postgraphile.custom_type.field_2\n is E’@name field_two\\nA description for the second field’;\n"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"现在，当查看模式时，"},{"type":"codeinline","content":[{"type":"text","text":"json"}]},{"type":"text","text":"字段不再显示为不透明的类型"},{"type":"codeinline","content":[{"type":"text","text":"JSON"}]},{"type":"text","text":"，而是显示为"},{"type":"codeinline","content":[{"type":"text","text":"CustomType"}]},{"type":"text","text":"："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/wechat\/images\/1d\/1dba321baa7f570c93e73652ac0be6b1.png","alt":null,"title":null,"style":null,"href":null,"fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"（还要注意，对视图所做的注解（"},{"type":"codeinline","content":[{"type":"text","text":"A description for the view"}]},{"type":"text","text":"）显示在查询字段的文档中）。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"单击"},{"type":"codeinline","content":[{"type":"text","text":"CustomType"}]},{"type":"text","text":"将显示自定义类型的字段及其注解："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/wechat\/images\/1a\/1a9259df888609e5fc1667bb2c4a906c.png","alt":null,"title":null,"style":null,"href":null,"fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"请注意，在自定义类型中，第二个字段被命名为"},{"type":"codeinline","content":[{"type":"text","text":"field_2"}]},{"type":"text","text":"，但 Graphile 智能注解将该字段重命名为"},{"type":"codeinline","content":[{"type":"text","text":"field_two"}]},{"type":"text","text":"，通过 Graphile 将驼峰式大小写转换为"},{"type":"codeinline","content":[{"type":"text","text":"fieldTwo"}]},{"type":"text","text":"。另外，对这两个字段的描述都被显示在生成的 GraphQL 模式中。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"允许 Graphile 生成的模式具有“所有权限”（在开发期间）"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"最初，当讨论使用 Graphile 作为“一种模式来管理所有模式”架构中的一个选项时，该提议遭到了强烈的反对。关于安全性（如何将其与我们的 IAM 基础设施集成，以及如何在数据库中实施行级访问控制？）和性能（如何限制查询以避免一次选择所有行来对数据库进行 DDoS 攻击？）的合法性问题引起了人们的关注，提出了使用类似于 SQL 的查询接口以提供对数据库表的打开权限（open access）。然而，在小团队快速开发内部应用程序的 GQLMS 环境中，默认的 Graphile 行为是让所有列都可用来过滤，这允许 UI 团队可以快速迭代大量新特性，而无需后端团队的参与。这与其他开发模型不同，在其他模型中，UI 和后端团队首先就初始 API 契约达成一致，后端团队实现 API，UI 团队使用 API，然后 API 契约随着 UI 需求在开发生命周期中的变化而演变。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"最初，整个应用程序的性能很差，因为 UI 通常需要多次查询才能获取所需的数据。然而，一旦应用程序的行为被充实起来，我们就可以快速创建新视图，以满足每个 UI 交互的需求，这样每次交互只需要一个调用即可。因为这些请求是以本机代码运行在数据库上，所以我们可以通过适当地使用索引、去规范化、集群等来执行复杂的查询并获得高性能。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"一旦 UI 和后端之间的“公共 API”（“public API”）固化，我们就“加固”了 GraphQL 模式，通过使用智能注解"},{"type":"codeinline","content":[{"type":"text","text":"@omit"}]},{"type":"text","text":"标记表和视图来删除所有不必要的查询（由 Graphile 的默认设置创建）。另外，Graphile 的默认行为是为表和视图生成突变，但是智能注解"},{"type":"codeinline","content":[{"type":"text","text":"@omit create，update，delete"}]},{"type":"text","text":"将从模式中删除突变。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"结论"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"对于那些采用模式优先方法进行 GraphQL API 开发中的用户来说，Graphile 的自动 GraphQL 模式生成功能可能会对模式设计者造成难以接受的限制。如果需要细粒度的访问控制，Graphile 可能很难集成到现有的企业 IAM 基础设施中。向 Graphile 生成的模式中添加自定义查询和突变（即公开 UI 所需的 gRPC 服务调用）是我们目前在 Docker 镜像中不支持的。然而，我们最近注意到 Graphile 的 makeExtendSchemaPlugin，它允许将自定义类型、查询和突变合并到 Graphile 生成的模式中。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"也就是说，在初始需求有限并且有一个临时的分布式团队（之前没有合作过）的情况下，一个内部应用在 4-6 周内就能成功实现，这引起了整个 Netflix Studio 的极大兴趣。Netflix 的其他团队也正在寻找对应的 GQLMS 方法："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"numberedlist","attrs":{"start":1,"normalizeStart":1},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":1,"align":null,"origin":null},"content":[{"type":"text","text":"使用标准的 GraphQL 构造函数和实用程序将数据库公开为 API"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":2,"align":null,"origin":null},"content":[{"type":"text","text":"利用自定义的 PostgreSQL 类型构建 GraphQL 模式"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":3,"align":null,"origin":null},"content":[{"type":"text","text":"通过从数据库自动生成大型 API 来提高灵活性"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":4,"align":null,"origin":null},"content":[{"type":"text","text":"并在 Graphile 生成的业务逻辑和数据类型之外，额外公开其他自定义的业务逻辑和数据类型"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"这是一个替代之前使用 REST 实现内部 CRUD 工具的可行解决方案。拥有托管 Graphile 的标准化 Docker 容器为团队提供了必要的基础设施，通过这些基础设施，他们可以快速迭代新工具的原型以及快速开发应用程序，从而解决全球媒体工作室在这个充满挑战时期内不断变化的需求。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"原文链接："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/netflixtechblog.com\/beyond-rest-1b76f7c20ef6","title":"","type":null},"content":[{"type":"text","text":"https:\/\/netflixtechblog.com\/beyond-rest-1b76f7c20ef6"}]}]}]}