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}}]}