Dubbo Architecture and Core Concepts

Tue, 25 Aug 2026 00:00:00 +0000

Dubbo’s core strength lies in its clear separation of responsibilities and its highly pluggable extension mechanism. Understanding the layering and the Invoker abstraction is the foundation for reading Dubbo’s source code and troubleshooting production issues.

Layered Architecture

From top to bottom Dubbo is divided into logical layers, each depending only on the interface (not the implementation) of the layer below:

service / config layer: the user-facing API and configuration layer, where @DubboService, @DubboReference, ReferenceConfig and ServiceConfig live.
proxy layer: generates dynamic proxies for service interfaces so remote calls are transparent to business code.
registry layer: encapsulates service registration and subscription, sensing provider/consumer up and down events.
cluster layer: wraps multiple Invokers into a “cluster Invoker”, responsible for load balancing, fault tolerance and routing.
protocol layer: encapsulates the RPC call; the core of Invoker export and reference.
filter chain: interceptors across the call path, usable for logging, auth, rate limiting and other cross-cutting concerns.

Invoker and SPI

Invoker is Dubbo’s universal domain model, representing “an executable and describable call”, abstracting local, remote and cluster invocations. URL acts as the configuration bus running through every layer; almost every extension point passes parameters via URL.

Service Registration and Discovery in Practice

Tue, 25 Aug 2026 00:00:00 +0000

Service registration and discovery are the foundation of microservice architecture. Dubbo abstracts the registry as the Registry interface, so you can switch smoothly between ZooKeeper, Nacos, Consul and others without changing business code.

Connecting a Registry

Using Nacos as an example, you only need to declare the registry address and protocol in configuration. On startup Dubbo automatically exports (export) and subscribes (subscribe) services:

dubbo:
 application:
 name: order-service
 registry:
 address: nacos://127.0.0.1:8848
 protocol:
 name: dubbo
 port: 20880

After a provider starts, it writes its metadata (interface, IP, port, weight, etc.) into the registry. When a consumer starts, it subscribes to the interface node, fetches the available provider list and caches it locally; subsequent calls go directly to the local cache, reducing registry pressure.

Dubbo on Zhuifeng Notes

Dubbo Architecture and Core Concepts

Layered Architecture

Invoker and SPI

Service Registration and Discovery in Practice

Connecting a Registry