Apache Dubbo: The Dubbo RPC Framework for Java

The challenge of inter-service communication

A Java team moving from a monolith to microservices needs more than a way to call methods across the network — it needs service discovery, load balancing, and traffic rules that don't come with plain gRPC or REST out of the box. Stitching those together from separate libraries (a registry client, a load balancer, a tracing agent) is its own project before you've shipped a single service.

What is Apache Dubbo?

Apache Dubbo is an RPC and microservice framework built primarily for Java, with implementations for Go, Python, PHP, Erlang, Rust, and Node.js, that bundles communication, service discovery, traffic management, observability, and security into one framework. It talks over its own Triple protocol (gRPC-compatible), the classic Dubbo2 TCP protocol, or REST, and connects to registries like Zookeeper or Nacos to find service instances.

Core features of Dubbo

• ✓Triple protocol: a Dubbo-native RPC protocol that's gRPC-compatible, so Dubbo services can also be called with a plain gRPC or cURL client — sits alongside legacy Dubbo2 TCP and REST for teams migrating gradually.
• ✓Pluggable service discovery through registries like Zookeeper or Nacos, with dynamic config, metrics, and tracing wired in rather than bolted on afterward.
• ✓Multi-language client support beyond Java: separate implementations exist for Go, Python, PHP, Erlang, Rust, and Node.js, letting non-Java services join the same Dubbo mesh.
• ✓A Spring Boot Starter that adds Dubbo to an existing Spring app with one dependency and a YAML config block, per the project's own getting-started guide.
• ✓REST support ships too, if that's all your team wants.
• ✓Kubernetes and service mesh integration, documented as a first-class deployment target rather than an afterthought.
• ✓Version 3.2.16 adds native image support and thread pool isolation; 3.3.x adds an affinity router, method-level TPS limiting, and a Spring 6 Security Plugin.

What you can build with Dubbo

• •Splitting a Java monolith into services that call each other over Triple/gRPC instead of internal method calls, without hand-rolling a discovery layer.
• •Enterprise microservice systems that need traffic management (canary releases, routing rules) and observability out of the box, per the project's core-features list.
• •Mixed-language service meshes where a Java backend needs to talk to Go, Python, or Node.js services using the same discovery and protocol layer.
• •Migrating an existing Dubbo2 TCP deployment to the Triple protocol incrementally, since Dubbo3 keeps both protocols available side by side.
• •Running services on Kubernetes with a service mesh, using Dubbo's documented Kubernetes & service mesh integration instead of assembling one from scratch.

Getting started with Dubbo and Spring Boot

The README points to two starting paths. For a minimal setup, its Lightweight RPC API lets you build RPC services with a small SDK and a 5-minute guide, choosing between the Triple, Dubbo2 (TCP), REST, or a custom protocol. For a Spring app, the Dubbo Spring Boot Starter is the documented path: add the starter dependency and a YAML config block, and the README says that alone wires up service discovery, observability, and tracing. Beyond the dependency and config file, the README does not walk through the YAML keys or a full working example inline — it links out to the docs site for that.

Adding Dubbo to your project

The README doesn't include a copy-pasteable Maven or Gradle snippet — it links out to the Spring Boot Starter task guide and a project template instead. What it does specify is compatibility: Dubbo 3.3.x needs JDK 1.8 through 21 (3.3.7-SNAPSHOT extends that to JDK 25), Dubbo 3.2.16 supports JDK 1.8–17, and the whole 2.x line is marked end-of-life. Pick a version off that compatibility table before adding it to a build file, since the older branches are no longer actively maintained.

Dubbo vs gRPC, Spring Cloud, and other RPC frameworks

Frequently asked questions

Who should try it — and who should skip

Try Apache Dubbo if you're a Java team already running several services with real inter-service traffic and want service discovery, traffic rules, and observability bundled instead of assembled from separate libraries — especially if you're on Zookeeper or Nacos already, or migrating off an old Dubbo2 TCP deployment onto Triple. Skip it for a small number of services talking over plain HTTP, or if your team doesn't want a second protocol stack alongside REST; a couple of gRPC or REST calls between two services doesn't need a full RPC framework wrapped around them.

Related repositories