Dubbo will actively seek to adapt to the SpringCloud ecosystem
Let me show you two pictures
Spring Cloud Alibaba is incubated as a Sub-project of Spring Cloud, with Dubbo as a feature. Dubbo was originally developed by author Liang Fei, and then dubbo went silent for several years. In 2017, Liu Jun took over to restart Dubbo. We also explained the relationship between Dubbo and Spring Cloud briefly in the Dubbo share at the Open Source China Year-end Gala. The first thing to be clear about is that Dubbo and Spring Cloud are not completely competitive, and they address different problem domains: Dubbo has always been positioned as an RPC framework, while Spring Cloud aims to be a one-stop solution under a microservices architecture. If I had to compare, I think Dubbo can be compared to Netflix OSS technology stack, while Spring Cloud integrates Netflix OSS as a distributed service governance solution, However, Spring Cloud also provides distributed problem solutions including Config, Stream, Security, SLEUTH, and so on. Due to RPC protocol, registry metadata mismatch and other issues, Dubbo and Spring Cloud are the only two choices when it comes to microservices infrastructure selection, which is one of the reasons why people always compare Dubbo and Spring Cloud. Dubbo will then actively seek to adapt to the Spring Cloud ecosystem, such as leveraging Dubbo’s performance benefits as a binary communication solution for Spring Cloud, or adapting Dubbo to Spring Cloud through modularity and SUPPORT for HTTP.
2. Dubbo and Feign have co-existed in SpringCloudAlibaba samples, and the specific usage depends on business needs.
Github.com/aliyun/alib…
github.com
