Why Dubbo 3.0 Became Alibaba’s Unified Cloud‑Native Service Framework

Background and Motivation

Alibaba treats a service framework as the railway tracks of a distributed system: interoperability at the framework level is required for higher‑level business integration. To provide a unified next‑generation service stack, Alibaba merged its internal HSF framework with the open‑source Dubbo, creating Dubbo 3.0 as the single standard for internal, commercial, and open‑source use.

Dubbo and HSF in Alibaba

Dubbo was created in 2008, open‑sourced in 2011, paused in 2014, revived as Dubbo 3.0 in 2017 and graduated to Apache in 2019. HSF, also released in 2008, evolved from a basic RPC library to a microservice framework that handles tens of trillions of calls and supports Java, C++, Node.js and PHP. Both co‑existed for years: HSF was chosen for its proven stability in high‑concurrency e‑commerce scenarios, while Dubbo grew into a widely adopted open‑source solution.

Emerging Cloud‑Native Challenges

Kubernetes has become the de‑facto scheduler and Service Mesh is the preferred way to hide infrastructure details, pushing enterprises to migrate to the cloud with minimal friction.

Multi‑cloud, multi‑language and multi‑environment deployments demand open standards for interoperability.

Rapid growth of client‑side calls to backend services expands the scale of microservice ecosystems.

These trends expose limitations in HSF (closed‑source, hard to debug) and Dubbo (protocol incompatibilities, divergent governance features).

Dubbo 3.0 Technical Enhancements

Introduces a highly compressed, cloud‑native service‑discovery model that aligns with mainstream Kubernetes designs, improving performance and cluster scalability.

Defines the Triple protocol – an HTTP/2‑based, fully gRPC‑compatible RPC protocol that simplifies multi‑language communication and is gateway‑friendly.

Provides a unified traffic‑governance model covering SDK deployment, Service Mesh, VM and container scenarios, allowing a single set of rules to govern heterogeneous environments.

Offers two Service Mesh integration modes: a thin SDK that mirrors mainstream Mesh deployments, and a proxy‑less mode that replaces sidecars by communicating directly with the control plane.

Zero‑Code Migration via Java Agent

Alibaba Cloud supplies a Java Agent based on the open‑source Arthas One Agent. The agent performs bytecode enhancement at runtime, enabling customers to adopt cloud services without modifying a single line of application code. Capabilities added by the agent include lossless service rollout, tag‑based routing, authentication, instance isolation and full‑link gray release.

Integration with Alibaba Cloud Service Governance (MSE/EDAS/SAE)

MSE (Microservice Engine), EDAS (Enterprise Distributed Application Service) and SAE (Serverless Application Engine) integrate Dubbo 3.0 out‑of‑the‑box. They provide open‑source‑compatible service discovery, testing, routing, monitoring and traffic‑governance without requiring custom tooling. The platforms support Dubbo 3.0 as well as legacy Dubbo and Spring Cloud applications, delivering zero‑code migration and seamless mesh compatibility.

Large‑Scale Production Case: DingTalk Documentation Migration

In 2020 DingTalk began a three‑month cloud migration. The strategy used two clusters (internal and cloud) with dual protocols: HSF + Triple internally, Triple only on the cloud. The migration plan:

Maintain a single codebase running on both clusters.

Keep HSF protocol for the internal cluster.

Expose the open‑source Triple RPC on the cloud cluster.

Enable bi‑directional communication between clusters.

Implementation steps:

Dual‑cluster deployment: Internal cluster kept version 1.0.0, cloud cluster used version 1.0.0.ZJK.

Unit‑level routing: HSF requests are intercepted; if the target resides in the cloud, a Triple call is issued, otherwise the request stays within the internal cluster.

Downstream dependency handling: Internal services are wrapped to expose Triple for cloud consumption.

Service governance: MSE provides service discovery, testing, routing and monitoring without custom tooling.

Result: Within three months DingTalk achieved full cloud operation, leveraging Dubbo 3.0’s cloud‑native features and MSE’s governance to maintain high availability during Double‑11 traffic peaks.

Upgrade Path for HSF Applications

For applications running on EDAS or SAE with the HSF + EDAS Container stack, upgrading the container runtime to version 4.x automatically migrates the HSF application to Dubbo 3.0. The upgraded application retains the original development model while gaining Dubbo 3.0 features such as application‑level service discovery and the Triple protocol.

Proxyless Mesh Architecture

Dubbo 3.0 supports two Mesh integration modes. In thin‑SDK mode, Dubbo acts as a lightweight client that relies on the existing Mesh data plane. In proxy‑less mode, Dubbo replaces the sidecar: it communicates directly with the Mesh control plane and applies the unified governance rules, eliminating the need for an additional Envoy sidecar.

Conclusion

Dubbo 3.0, together with the HSF 3.0 adaptation layer, provides a unified, cloud‑native microservice framework that serves internal Alibaba services, Alibaba Cloud customers and the open‑source community. Its compressed service‑discovery model, Triple protocol, unified traffic‑governance and flexible Mesh integration enable seamless migration, high performance and consistent governance across heterogeneous environments.