Dubbo makes Apache top project news

Dubbo in the Apache home page software list

History of Dubbo

On October 27, 2011, Alibaba opened the core framework Dubbo of its servitization governance scheme, and the design concept of service governance began to be gradually implemented and widely used in the domestic software industry. Since open source, many non-Alibaba companies have chosen to use Dubbo, including Internet companies such as Dangdang and Netease Kaola, as well as traditional enterprises such as China Life Insurance and Qingdao Haier.

After Dubbo 2.5.3 was released on October 23, 2012, Alibaba basically stopped major upgrades to Dubbo just before Dubbo’s one-year anniversary of open source.

In 2013, 2014, the maintenance version of Dubbo 2.4 was updated 2 times, then all maintenance work was stopped. At this point, Dubbo’s support for Spring remains at Spring 2.5.6.

During the period when Ali stopped maintaining and upgrading Dubbo, Dangdang began to maintain its own Dubbo branch version Dubbox. The new features mainly include: support the new version of Spring, support Rest protocol, etc., and open source Dubbox. Meanwhile, Kaola.com also maintains its own independent branch, Dubbok, which is not open source.

Dubbo quietly released version 2.5.4 on GitHub on September 7, 2017. It was quickly followed by versions 2.5.5, 2.5.6, 2.5.7, etc. At the Cloud Conference in October, Alibaba announced that Dubbo had been listed as one of the group’s key open source maintenance projects, which means that Dubbo is back on the fast track.

On January 8, 2018, Dubbo version 2.6.0 was released. The new version merged Dubbox, which was previously open source of Dangdang, and realized the unified integration of Dubbo versions.

On February 9, 2018, a vote was held on the Apache Foundation mailing list to discuss whether to admit Ali’s Dubbo project into the Apache Incubator. After a week of voting, the mailing list showed that Dubbo received 14 votes in favor, and with no abstentions or negative votes, was officially voted into the Apache Foundation incubator program.

Since then, Dubbo has started two long-term maintenance versions, Dubbo 2.6.x (package name: com.alibaba) stable maintenance version and Dubbo 2.7.x (package name: org.apache) Apache incubation version.

In 2018 and 2019, Dubbo released 4 or 5 versions and released nodeJS, Python, Go and other multi-language clients. During this period, the Dubbo community has held developer salons in Beijing, Shanghai, Shenzhen, Chengdu, Hangzhou, Nanjing and other cities.

In January 2019, release 2.7.0 was released. This graduating apache release supports a wealth of new features, the all-new Dubbo Ops console. In May, Dubbo arrived at version 2.7.2, during which new features were actively introduced to support registries such as Consul, NACOS, ETCD, etc.

On May 21, 2019, After a long incubation period, Dubbo finally graduated, and another open source masterpiece of Alibaba became Apache’s top project.

dubbo or springcloud

Before SpringCloud came out, Dubbo was almost the standard of SOA in China. In my memory, there has never been a domestic open source software favored and chosen by so many companies. Companies using Dubbo include but are not limited to: Dangdang, Wangyi Kaola, VIVO, Didi, Qunar, Yummy, TCL, etc. (reference: github.com/apache/incu…

Dubbo and SpringCloud, in fact, are not comparable. Dubbo is an RPC framework (and while Dubbo is also going ecological, it’s barely in its infancy), SpringCloud is a microservices solution. In my opinion, Dubbo can only compare some of the features of Spring Cloud Netflix, a well-known solution in Spring Cloud.

Dubbo or springcloud? Dubbo is perfectly compatible with SpringCloud, as shown in the architecture below (from the Technology Exchange Group). So using SpringCloud doesn’t mean the project is advanced, and using Dubbo doesn’t mean the project is backward. Microservices are so large and complex that even SpringCloud can’t cover every step of the way, and some of springCloud’s existing solutions don’t work well or even meet production standards. What we need to do is to select the most beneficial open source product for our project based on each technical link and our own business characteristics, rather than just the SpringCloud system:

Transfer: mp.weixin.qq.com/s/vq5F4a0vx…