What is this?
Apache Dubbo is an RPC and microservices framework — this repository is its Java implementation. It covers communication, service discovery, traffic management, observability, security, and tooling for building enterprise-grade microservices.
Apache Dubbo is an RPC and microservices framework — this repository is its Java implementation. It covers communication, service discovery, traffic management, observability, security, and tooling for building enterprise-grade microservices.Is this just a Java library, or a bigger framework?It is a full Web and RPC framework rather than a small library — and Java is not the only flavor: Dubbo also ships for Go, Python, PHP, Erlang, Rust, and Node.js/Web. This repo holds the Java one.
It is a full Web and RPC framework rather than a small library — and Java is not the only flavor: Dubbo also ships for Go, Python, PHP, Erlang, Rust, and Node.js/Web. This repo holds the Java one.How do I get a first service running?Two routes: a lightweight RPC API with a minimal codebase (there is a 5-minute guide), or the Spring Boot Starter — one dependency plus a YAML config unlock service discovery, observability, and tracing.
Two routes: a lightweight RPC API with a minimal codebase (there is a 5-minute guide), or the Spring Boot Starter — one dependency plus a YAML config unlock service discovery, observability, and tracing.Which JDK version do I need?It depends on the Dubbo line: 3.3.6 supports JDK 1.8-21 (3.3.7 snapshots add JDK 25), while 3.2.16 tops out at JDK 17, and legacy 2.6.x/2.5.x ran on JDK 1.6-1.7.
It depends on the Dubbo line: 3.3.6 supports JDK 1.8-21 (3.3.7 snapshots add JDK 25), while 3.2.16 tops out at JDK 17, and legacy 2.6.x/2.5.x ran on JDK 1.6-1.7.Is the old Dubbo2 line still safe to start a new project on?No — Dubbo2 releases (2.7.23 and older 2.6.x/2.5.x) are end-of-life, and even 3.1.11 is stable but no longer actively maintained. Pick 3.3.x or 3.2.x for active support.
No — Dubbo2 releases (2.7.23 and older 2.6.x/2.5.x) are end-of-life, and even 3.1.11 is stable but no longer actively maintained. Pick 3.3.x or 3.2.x for active support.What protocols can my services talk over?Triple (gRPC-compatible and testable with cURL), the classic Dubbo2 protocol over TCP, REST, or a custom protocol of your own.
Triple (gRPC-compatible and testable with cURL), the classic Dubbo2 protocol over TCP, REST, or a custom protocol of your own.How do services find each other at runtime?Consumers dynamically discover provider instances through a registry such as Zookeeper or Nacos, and traffic between them follows strategies you define.
Consumers dynamically discover provider instances through a registry such as Zookeeper or Nacos, and traffic between them follows strategies you define.Does it integrate with Kubernetes and service meshes?Yes — Kubernetes and service mesh support is one of the documented hands-on areas, alongside traffic management, observability, extensibility, and security.
Yes — Kubernetes and service mesh support is one of the documented hands-on areas, alongside traffic management, observability, extensibility, and security.Is there an admin console for managing services?Yes — Dubbo ships built-in support for a visualized console alongside dynamic config, metrics, tracing, and security.
Yes — Dubbo ships built-in support for a visualized console alongside dynamic config, metrics, tracing, and security.What are similar projects?spring-cloud-alibaba, apisix, brpc, istio, linkerd2, nacos, Sentinel, go-zero
spring-cloud-alibaba, apisix, brpc, istio, linkerd2, nacos, Sentinel, go-zeroWhich topics is it in?restful, service-mesh, dubbo, apache, tcp, reactive, rest, rpc, spring-boot, grpc, microservices, best-practices
restful, service-mesh, dubbo, apache, tcp, reactive, rest, rpc, spring-boot, grpc, microservices, best-practices