愛奇藝微服務標準技術架構實踐

{"type":"doc","content":[{"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":"爲數以億計的用戶提供優質的視頻服務的愛奇藝技術產品團隊，爲了適應業務的快速迭代和創新，並支撐海量的用戶請求，很多團隊都對各自的業務系統自發地進行了微服務架構的改造。"}]},{"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":"在微服務化的過程中，各業務團隊根據自身需要選擇了不同的開源框架，如Apache Dubbo\/Spring Cloud等，此外也存在一些自研性質的框架；另外爲了滿足對微服務應用的監控等需求，不少團隊還自行維護了監控系統等基礎設施。"}]},{"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":"·部分基礎設施存在重複建設，在資源浪費的同時穩定性也不易保證；"}]},{"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":"·由於使用的技術架構和SDK不統一，最佳實踐難以在團隊間快速推廣；"}]},{"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":"爲了解決以上問題，愛奇藝中間件團隊充分聽取了業務在微服務實踐中的需求和問題，推出了愛奇藝的微服務標準架構。在標準架構的建設過程中，我們主要遵循了以下的一些原則："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}}]}