Nacos as Dubbo ecosystems important registry implementation, including dubbo-registry-nacos is Dubbo fusion Nacos registry implementation.
When you put dubbo-registry-nacos integrated into your dubbo project before, please make sure the background nacos service has started. If you are still not familiar with the basic use of Nacos, reference Quick Start for Nacos.
Nacos Dubbo fusion become registry procedure is very simple, general steps can be divided into “increasing Maven dependency” and “the registry”.
Increasing Maven dependency
First, you need to dubbo-registry-nacosMaven dependent on added to your project pom.xml file, and strongly recommend that you use the dubbo 2.6.5:
When a project to adddubbo-registry-nacos, you don’t need to explicitly logic programming to realize service discovery and registration, actual implementation is provided by the third party and then configure Naocs registry.
Suppose you Dubbo application using the Spring Framework assembly, there will be two kinds of optional configuration method, respectively: Dubbo Spring externalized configuration, and the Spring XML configuration files, and, I strongly recommend the former.
Dubbo Spring externalized configuration
Dubbo Spring externalized configuration consists of Dubbo 2.5.8 introduced new features, through the Spring Environment attribute automatically generate and bind the Dubbo configuration Bean, implement configuration to simplify, and lower the threshold of service development.
Suppose you Dubbo applications using Nacos as registry, and the server IP address is:10.20.153.10 at the same time, the registered address as Dubbo externalized configuration properties are stored in dubbo-config.properties file, as shown below:
Then, restart your application Dubbo, Dubbo information services and consumption in Nacos console can show:
As shown, the service name prefix for providers: metainfo for the service provider’s information, consumers: represents the service consumer metainfo. Click”details” can check the service status details:
If you are using a Spring XML configuration file assembly Dubbo registry, please refer to the next section.
Spring XML configuration files
Similarly, suppose you Dubbo applications using Nacos as registry, and the server IP address is:10.20.153.10, and assembling Spring Bean in the XML file, as shown below:
After restart the Dubbo application, you can also find the provider and consumer registered metainfo is presented in Nacos console:
Whether you absolute configuration or switch Nacos registry super Easy? If you are still wanting more or less understand, may refer to the following the complete example.
Above pictures of metadata from Dubbo Spring annotations driver sample and Dubbo Spring XML configuration driven example, the following will introduce both, you can choose your preference programming model.Before the formal discussion, first to introduce the preparation work, because they are dependent on the Java service interface and implementation.At the same time, please make sure that the local (127.0.0.1) environment has launched Nacos service.
Sample interface and implementation
First define the sample interface, as shown below:
Provide the above interface implementation class:
Interface and implementation after ready, the following will be driven by annotations and XML configuration driven their implementation.
Dubbo 2.5.7 reconstructed the Spring annotations driver programming model.
Provider annotation driven implementation
Definition of Dubbo provider externalized configuration properties - provider-config.properties
Implement the provider to guide class - DemoServiceProviderBootstrap
The annotation @EnableDubbo activation Dubbo annotation driven and externalized configuration, its scanBasePackages properties scanning to specify the Java package, all marked @Service Service interface implementation class exposure for Spring Bean, then be exported Dubbo Service.
@PropertySource is Spring Framework 3.1 introduced the standard import properties annotation configuration resources, it will provide Dubbo externalized configuration.
Service consumer comments drive implementation
Definition of Dubbo consumer externalized configuration properties - consumer-config.properties
Similarly, dubbo.registry.address attribute points to Nacos registry, other dubbo service relevant meta information through Nacos registry access.
Similarly, @EnableDubbo annotations to activate Dubbo annotation driven and externalized configuration, but the current belong to the Service consumers, without having to specify the Java package name scan label @Service Service implementation.
@Reference is Dubbo remote service dependency injection annotations, need service providers and consumers agreed interface (interface), version (version) and group (group) information.Example, in the current service consumption DemoService service version from the configuration properties file consumer-config.properties.
@PostConstruct code shows when DemoServiceConsumerBootstrap Bean initialization, execution Dubbo ten times remote method invocation.
Run annotation driver sample
Twice in the local boot DemoServiceProviderBootstrap, the registry will appear two health services:
Run again DemoServiceConsumerBootstrap, run results as follows:
Operate, and service consumer using the load balancing strategy, RPC calls ten times the average contribution to two Dubbo provider instance.
Spring XML configuration driver sample
The Spring XML configuration driven programming model is a traditional Spring assembly components.
Provider XML configuration
Define the service provider XML context configuration file - /META-INF/spring/dubbo-provider-context.xml
Implement the provider to guide class - DemoServiceProviderXmlBootstrap
Service consumer driven XML configuration
Define the service consumer context XML configuration files - /META-INF/spring/dubbo-consumer-context.xml