解读微服务的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 的前期应用、后期维护均造成一定困难。"}]}]}