解讀微服務的2020：框架在左網格在右，雲原生時代的微服務路在何方？

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"微服務的 2020，有堅守有破局。服務框架依然在持續進化和奔向雲原生，Service Mesh 在持續進步的同時依舊疑點重重。總體而言，微服務架構的演進並非一蹴而就，過於保守或激進都不是解決之道。長期修行，苦練內功，或許纔是微服務架構的前路方向。"}]},{"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":"2020 年，微服務這一持續多年的話題熱度依舊：以 Spring Cloud、Dubbo 爲代表的服務框架依然在持續進化，並加速奔向雲原生；Service Mesh 這一雲原生、微服務雙圈“網紅”依然在迷霧中砥礪前行。對大多數企業而言，面對雲原生和微服務技術的蓬勃發展，不免有些疑惑：一邊是成熟演進的服務框架，一邊是代表未來方向的 Service Mesh，企業的架構演進方向究竟該如何選擇？"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服務框架：進化與困局"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"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":"Spring Cloud 之於微服務體系，就像 Spring 之於 Java 開源框架：地位舉足輕重。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.geekbang.org\/wechat\/images\/37\/370ef167aaf38d5366bfccb6089dea05.jpeg","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":"在微服務生態圈，Spring Cloud 像一個武器庫，具備了大量解決分佈式、微服務場景問題的“武器”。目前的 Spring Cloud 項目下，已經有超過 30 個子項目，有些子項目下還包括了功能豐富、數量可觀的的子模塊。一方面，得益於此的開發者可以方便的複用已有的開源能力，無需重複造輪子；另一方面，Spring Cloud 的初學者需要付出較多代價去學習框架本身的使用姿勢與特性，這給 Spring Cloud 的前期應用、後期維護均造成一定困難。"}]}]}