Today, I saw such a problem in Zhihu ：Spring Cloud and Dubbo Which one will be eliminated ？ After reading a few answers , I don’t think it’s on the point , So either just write a little article and talk about it .
Just a little bit of personal opinion
I think these two frameworks will exist for a long time .
today , These two frames are now , There’s no such thing as who will replace whom . because Spring Cloud Alibaba Appearance ,Dubbo It’s very well integrated into Spring Cloud system , So around Spring Cloud All kinds of ecological peripheral products can be seamlessly integrated to play together .
Dubbo Seamless integration Spring Cloud What does ecology mean ？ There are two main aspects ：
- If you were Dubbo user , Now you can put Spring Cloud Bring in . Integrate… Easily and easily Spring Cloud Configuration center 、 Registry and useful peripheral products such as distributed tracking to manage your distributed service cluster , And others Spring Cloud Netflix Users enjoy the same ecological advantages .
- If you’re not Dubbo user , But your scene is using HTTP When calling, I feel that it is not efficient and economical , Then we can consider introducing Dubbo, To improve your service calls RPC performance .
Come here , Maybe some of the watchmen have to say , You’re all from the perspective of integration , I just don’t like Dubbo The way the interface depends , Firmly defend Spring Cloud Primitive ecology ！
That’s ok ！ This kind of persistence is OK , There’s nothing wrong with it , adopt HTTP Contract management service interface , No interface provider JAR, There is no coupling at the compile level , It’s true that this has always been unnecessary at the moment Dubbo An important argument for . I also feel that this choice has advantages in many aspects , But there are also very high requirements for the compatible design of the interface , As long as it can be executed in place , Any one of them can be done smoothly .
however , In my submission Spring Cloud The user’s insistence on this solution does not affect Dubbo The extinction of Ecology . Two main points ：
- Dubbo The original user base is huge , stay Spring Cloud Before the sermon ,Dubbo It has a huge user base , Now that there is a good integration plan , Then the consideration of fusion is more secure than that of reconstruction .
- There are a lot of users will question Alibaba’s open source project easy eunuch , This time, Dubbo Re maintain , How long can it last ？ In fact, we don’t have to worry about this too much this time , Because the current Dubbo It has been given to Apache The foundation , because Apache There are high requirements on the evaluation of whether open source projects can be maintained for a long time （ Activity level 、 Contribution ratio, etc ）, Can be in Apache Graduation project , Unless something comes up that can surpass it in every way , Otherwise, it will exist for a long time and apply .
No matter from Spring Cloud Users , still Dubbo Users , There are no scenes that absolutely want to die out of the other side . therefore , I think these two are very likely to be good foundation friends , Especially in the domestic application .
What about these two popular frameworks , Do you have a different point of view ？
Welcome to my official account. 「 Program the ape DD」 Or my blog ：didispace.com, Long term serialization Spring Boot And Spring Cloud Original content sharing . This article was first published on my independent blog ：Spring Cloud and Dubbo Which one will be eliminated ？, Reprint please indicate the source .