Netflix Android应用的API后端怎样从单体无缝切换到微服务？

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"本文最初发布于Netflix技术博客，经授权由InfoQ中文站翻译并分享。"}]},{"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":"作为Android开发人员，我们通常可以将后端视为在云中运行的黑盒，负责忠实地向我们返回JSON。在Netflix，我们采用了服务于前端的后端（Backend for Frontend，BFF）模式：我们没有一个通用的“后端API”，而是每个客户端（Android\/iOS\/TV\/web）有一个后端。在Android团队中，尽管我们大部分时间都花在了应用程序上，但还要负责维护与应用程序通信的后端及其编排代码。"}]},{"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":"text","text":"我们以前用的本质上是单体服务中的无服务器模型，现在则要部署和维护一个托管我们应用程序后端端点的全新微服务。这让Android工程师对我们获取数据的过程有更多的控制权和可观察性。"}]},{"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":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"背景"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}}]}