Unlocking Dubbo: Inside Alibaba’s RPC Framework and Its Future Roadmap

Dubbo’s Basic Principles

Dubbo is a Java‑based RPC framework consisting of four roles: service provider, service consumer, registry, and monitoring center.

It operates in deployment and runtime phases. During deployment, providers expose services and register their addresses; consumers subscribe to those addresses. At runtime, the registry pushes address lists to consumers, which select an address for an RPC call, while both sides report status to the monitor.

The overall architecture is divided into nine layers, separating user‑facing biz, core RPC, and remoting, with APIs for users and SPI for extensions.

Design Principles

Dubbo follows high cohesion and low coupling, with clear layer separation and unidirectional dependencies, avoiding circular references. It treats third‑party extensions as first‑class citizens, allowing built‑in features and external extensions to replace each other, fostering an extensible ecosystem.

Open‑Source Status

Since its revival in July 2017, Dubbo’s GitHub stars grew 77% to 18 000, ranking 11th among Java projects and entering the Apache Incubator in February 2018.

It is used by Alibaba, Didi, Dangdang, large enterprises such as ICBC, China Telecom, China Life, and ISVs like AsiaInfo and Wensi.

Future Plans & Apache Incubation

Upcoming work focuses on modularization and metadata to prepare for microservices and cloud‑native environments, enhancing service governance, routing strategies, flow control, and large‑scale cluster handling, as well as adding async support with CompletableFuture and Reactive Streams.

The incubation process includes preparation, incubation, and graduation stages; after meeting Apache’s maturity criteria, Dubbo aims to become a top‑level Apache project.

For more details and expert guidance, attend the Dubbo developer salon in Beijing.