Today I saw such a question on Zhihu: Which will be eliminated, Spring Cloud or Dubbo? Read a few answers, all feel not on the point, so or simply write a short article blind force talk about.

A brief personal opinion

I think both frameworks are likely to be around for a long time.

Up to now, the two frameworks in the present, there is no one to replace who said. Due to the emergence of Spring Cloud Alibaba, Dubbo has been well integrated into the Spring Cloud system, so various peripheral products surrounding the Spring Cloud ecosystem can be seamlessly integrated to play.

What does Dubbo mean by seamlessly integrating the Spring Cloud ecosystem? There are two main aspects:

  1. If you are a Dubbo user, Spring Cloud is now available. Easily integrate Spring Cloud’s configuration center, registry, and nice peripheral products such as distributed tracking to manage your distributed service cluster, enjoying the same ecological advantages as other Spring Cloud Netflix users.
  2. If you are not a Dubbo user, but your scenario is not efficient or economical when using HTTP calls, consider introducing Dubbo to improve RPC performance for your service and calls.

I just don’t like Dubbo’s interface-dependent approach. I firmly defend the original ecosystem of Spring Cloud!

Line! There is nothing wrong with this insistence. Managing the service interface through HTTP contracts without the JAR of the interface provider creates no coupling at the compile level, which has indeed been an important argument for not using Dubbo at this point. Personally, I think this option has advantages in many aspects, but it also has very high requirements on the compatible design of the interface. As long as it can be implemented in place, any scheme can be done smoothly.

However, I don’t think the persistence of Spring Cloud users for this solution will affect the demise of the Dubbo ecosystem. Two main points:

  1. Dubbo’s original user base is huge, and Dubbo had a huge user base before Spring Cloud launched, and now that there’s a good convergence solution, it’s definitely safer to think about convergence than refactoring.
  2. There are many users who doubt that Alibaba’s open source project is too easy to be a slave. How long can Dubbo maintain it again? In fact, there is no need to worry too much this time, because the current Dubbo has been given to the Apache Foundation. Since Apache has high requirements on the evaluation of whether open source projects can be maintained for a long time (active degree, contribution ratio, etc.), the project that can be graduated from Apache, unless there is something that can surpass it in all aspects, Otherwise it will exist and apply for a long time.

For both Spring Cloud users and Dubbo users, there is no absolute death scenario. Therefore, PERSONALLY, I think these two are very likely to become good gay friends, especially in domestic applications.