Address Discovery on Apache Dubbo

Using Nacos as the Registry

Mon, 01 Jan 0001 00:00:00 +0000

This example shows dubbo-go’s service discovery feature with Nacos as the registry. You can view the complete example source code in dubbo-go-samples.

How to Start

Start the Nacos Server

Follow this instruction to install and start the Nacos server.

Server Registration Configuration

API Configuration

ins, _ := dubbo.NewInstance(
		dubbo.WithName("dubbo_registry_nacos_server"),
		dubbo.WithRegistry(
			registry.WithNacos(),
			registry.WithAddress(nacosAddr),
		),
		dubbo.WithProtocol(
			protocol.WithTriple(),
			protocol.WithPort(20000),
		),
	)

The meaning of each configuration item is as follows:

Using ZooKeeper as a registry

Mon, 01 Jan 0001 00:00:00 +0000

This guide explains how to use ZooKeeper as a registry in Dubbo-Go. The complete example is available in the dubbo-go-samples/registry/zookeeper directory.

Start ZooKeeper

Start with Docker

Run a local ZooKeeper instance with Docker:

docker run --name dubbo-go-zookeeper --rm -d -p 2181:2181 zookeeper:3.9.5

Confirm that the container is running:

docker ps --filter name=dubbo-go-zookeeper

Start from a binary distribution

Download a binary distribution from the ZooKeeper releases page. Extract the archive, copy the sample configuration, and start the service:

Application-level Service Discovery

Mon, 01 Jan 0001 00:00:00 +0000

Dubbo-go supports both interface-level registration and application-level service discovery. Interface-level registration stores callable provider URLs directly in the registry. Application-level service discovery stores application instances in the registry, and uses service mapping plus metadata to recover the provider URLs required by consumers.

Application-level service discovery is the current default model. Interface-level registration and application-level service discovery use different registration and subscription paths, and they are not automatically interoperable. A consumer using interface-level discovery cannot discover providers that only register application-level instances; a consumer using application-level discovery cannot discover providers that only register interface-level URLs. Use all during migration if both consumer types must be supported.

Multiple Registration Centers

Mon, 01 Jan 0001 00:00:00 +0000

A Dubbo application can configure multiple registration centers at different interface dimensions. Multiple registration centers can be used for cluster isolation, migration, and various other scenarios. For a more detailed explanation, refer to the Dubbo Java Multiple Registration Center Documentation.

Usage Scenarios

Migration Scenario

Migrate smoothly between different registration centers without service interruption. For example, when migrating from ZooKeeper to Nacos, dual registration keeps the business running during the transition.

Canary Release Scenario

Deploy an independent canary registration center so that only specific traffic can access the testing version. The new version is registered to the canary center first, and after validation passes, it is released to all traffic, reducing the risk of going live.