Dubbo 3.0 is coming.

On January 8, 2018, Liang Fei, one of the founders of Dubbo, revealed in the Dubbo Chat group that Dubbo 3.0 is under construction.

Dubbo is the distributed framework of Ali open source, which has been in a half-dead state for many years and started to be updated again in 2017. Dubbo has been in the stage of small and fast running since its resurrection, but now it has brought such a major change in 3.0, so that people pay more attention to the development of Dubbo, hope that Dubbo truly complete nirvana rebirth!

Dubo3.0 is currently in full development, with initial Runtime verification underway and the online application ready for use by the end of March, according to reliable sources online.

A preview of new features in Dubbo 3.0

According to sources, the Dubbo 3.0 kernel is completely different from Dubbo 2.0, but it will be 2.0 compatible.

Dubbo 3.0 will feature Streaming as the core rather than RPC of the 2.0 era, but RPC will become an optional form of remote Streaming docking in 3.0. Dubbo 3.0 provides a kernel interface, Streamingdocking(Streaming), around which all service governance will be extended. The Streaming channel is similar to gRPC in that it supports HTTP/2, while the REST interface is also supported by first-class citizens.

Dubbo 3.0 does not change much in communications, but focuses on service governance and programming models. Speaking of the innovation of the programming model, liang fei revealed that the Dubbo3.0 can be started mainly because the new features will remove all blocks, with “all synchronization” as the first goal, in the IO intensive business processing, it can improve the utilization rate of the machine, so that half of the cost of the machine is saved. In fact, he said, the driving factor for major changes in the selection of Dubbo 3.0 technology was cost reduction, because after the system was servitized, machines across the line of business were waiting for data to return, and the load was not up, and the machines were wasted.

In Dubbo3.0, Reactive will be at the core and will be able to do everything from client and server to cache and database without blocking. On the database, changes will be made to the JDBC driver, along with improvements to the JVM coroutine using Alibien for performance. More importantly, this significant change is not just in Dubbo, it will also affect alibaba’s 10 years of accumulated middleware.

Someone in the group asked if Service Mesh would be adopted. Liang fei said Dubbo 3.0 will support optional Mesh and add another layer of IPC, mainly for compatibility with older systems. Internally, the embedded mode will be tried first. He said the proxy mode Ops can independently upgrade the framework and reduce business intrusion, while the embedded mode can provide business testing, fewer nodes to deploy, and easier stability testing. At the same time, Dubbo 3.0 can be started as an independent process. Dubbo – Mesh is used to conduct IPC, and routing, load balancing, and fusing mechanism are controlled by the independent process.

Given Dubbo 3.0’s new features, we’ll have to wait and see!

Related Posts

Spring Security Actual Action: Initialization details of AuthenticationManager

Redis-BitMap

Java Things most people don’t know – Introspector and PropertyDescriptor