How to Enable Dubbo Application‑Level Service Discovery in 2.7.5

Dubbo Application‑Level Service Discovery Overview

When a Dubbo provider starts, it registers with a registry center, and consumers retrieve services from that registry. Traditionally, Dubbo registers data at the interface level; the new application‑level discovery registers instances (IP + port), offering finer granularity.

Reasons for this change include aligning with mainstream microservice models such as Spring Cloud and Kubernetes native services, and reducing registration data to improve performance.

Why This Article Was Written

Dubbo version 2.7.5 introduced application‑level service discovery, but the official release note only mentions support for a new discovery granularity and that it is still in BETA, without any usage documentation. Existing articles only discuss principles, so this guide demonstrates a practical configuration and demo.

Experience Application‑Level Service Discovery

Environment Setup

Only a Zookeeper instance is needed as the registry. Use Docker to start Zookeeper:

docker pull zookeeper
docker run -p 2181:2181 -d zookeeper:latest

Clone the Dubbo source code:

git clone https://github.com/apache/dubbo.git

The project includes demos that can be run with annotations, API, or XML configurations.

Two Types of Service Discovery

Interface‑Level Service Discovery

Dubbo registers services at the interface level by default. After starting a provider demo, you can view the registration data in Zookeeper under /dubbo:

The registered node contains metadata such as IP, port, interface, and methods.

Application‑Level Service Discovery

Configuration for application‑level discovery is scarce. Besides setting the Zookeeper address, you must enable the service‑level registry type:

dubbo.registry.parameters[registry-type]=service

Java configuration example:

RegistryConfig registryConfig = new RegistryConfig("zookeeper://127.0.0.1:2181");
Map<String, String> params = new HashMap<>();
params.put("registry-type", "service");
registryConfig.setParameters(params);

Both provider and consumer need this configuration. The consumer also must set the target application name on the reference:

ReferenceConfig<DemoService> reference = new ReferenceConfig<>();
reference.setInterface(DemoService.class);
reference.setGeneric("true");
reference.setServices("dubbo-demo-api-provider");

RegistryConfig registryConfig = new RegistryConfig("zookeeper://127.0.0.1:2181");
Map<String, String> params = new HashMap<>();
params.put("registry-type", "service");
registryConfig.setParameters(params);

After applying this configuration, registration data appears under /services in Zookeeper:

The service‑level metadata disappears, so the consumer first establishes a connection with the provider and then retrieves metadata.

Conclusion

This article demonstrates Dubbo's new application‑level service registration and discovery capabilities, aligning it with other microservice discovery models. Further exploration is needed to apply this feature effectively in real‑world scenarios.