nacos注册中心源码解析(一)

 

 

说道源码解析，那就不得不把源码从git上下载下来,所以想要深入的童鞋一定要把源码给下载下来。

那么接下来就直接开始吧！

那么从哪开始呢?我们日常使用当然是启动nacos，然后在一个springboot配置中添加nacos服务发现的一个jar包，我们项目用的是2.2.3版本的

<dependency>
    <groupId>com.alibaba.cloud</groupId>
    <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
</dependency>
       

那么之后呢? 如果对springboot自动配置原理有些了解的小伙伴会知道，springboot在启动的时候会扫描jar包中META-INF/spring.factories这个文件，如下是nacos-discovery jar包中的spring.factories文件

org.springframework.boot.autoconfigure.EnableAutoConfiguration=\
  com.alibaba.cloud.nacos.discovery.NacosDiscoveryAutoConfiguration,\
  com.alibaba.cloud.nacos.ribbon.RibbonNacosAutoConfiguration,\
  com.alibaba.cloud.nacos.endpoint.NacosDiscoveryEndpointAutoConfiguration,\
  com.alibaba.cloud.nacos.registry.NacosServiceRegistryAutoConfiguration,\
  com.alibaba.cloud.nacos.discovery.NacosDiscoveryClientConfiguration,\
  com.alibaba.cloud.nacos.discovery.reactive.NacosReactiveDiscoveryClientConfiguration,\
  com.alibaba.cloud.nacos.discovery.configclient.NacosConfigServerAutoConfiguration,\
  com.alibaba.cloud.nacos.NacosServiceAutoConfiguration
org.springframework.cloud.bootstrap.BootstrapConfiguration=\
  com.alibaba.cloud.nacos.discovery.configclient.NacosDiscoveryClientConfigServiceBootstrapConfiguration

从上述我们看到这个jar包配置了挺多的自动配置类，有什么ribbon，nacos的也很多，怎么看呢？这里凭借经验或者理解来说是这个NacosServiceRegistryAutoConfiguration类，nacos服务注册自动配置，那么我们点进去

@Configuration(proxyBeanMethods = false)
@EnableConfigurationProperties
@ConditionalOnNacosDiscoveryEnabled
@ConditionalOnProperty(value = "spring.cloud.service-registry.auto-registration.enabled",
		matchIfMissing = true)
@AutoConfigureAfter({ AutoServiceRegistrationConfiguration.class,
		AutoServiceRegistrationAutoConfiguration.class,
		NacosDiscoveryAutoConfiguration.class })
public class NacosServiceRegistryAutoConfiguration {

	@Bean
	public NacosServiceRegistry nacosServiceRegistry(
			NacosDiscoveryProperties nacosDiscoveryProperties) {
		return new NacosServiceRegistry(nacosDiscoveryProperties);
	}

	@Bean
	@ConditionalOnBean(AutoServiceRegistrationProperties.class)
	public NacosRegistration nacosRegistration(
			ObjectProvider<List<NacosRegistrationCustomizer>> registrationCustomizers,
			NacosDiscoveryProperties nacosDiscoveryProperties,
			ApplicationContext context) {
		return new NacosRegistration(registrationCustomizers.getIfAvailable(),
				nacosDiscoveryProperties, context);
	}

	@Bean
	@ConditionalOnBean(AutoServiceRegistrationProperties.class)
	public NacosAutoServiceRegistration nacosAutoServiceRegistration(
			NacosServiceRegistry registry,
			AutoServiceRegistrationProperties autoServiceRegistrationProperties,
			NacosRegistration registration) {
		return new NacosAutoServiceRegistration(registry,
				autoServiceRegistrationProperties, registration);
	}

}

可以看到这里注册了三个bean，这三个bean有什么关系呢，我们逐一点击去看下继承关系中可以得到如下结果

这里稍微解释，继承了applicationListener接口需要实现onApplicationEvent这个方法，他会监听对应的事件，这里我把WebServerInitializedEvent的注释带上了，意思就是在事件在web服务准备好了就会被发布。

顺着我图中的顺序，我们来到NacosServiceRegistry.register(Registration registration)方法

        NamingService namingService = namingService();
        String serviceId = registration.getServiceId();
		String group = nacosDiscoveryProperties.getGroup();

		Instance instance = getNacosInstanceFromRegistration(registration);

		try {
            //从方法名称来看是注册实例，我们点进去
			namingService.registerInstance(serviceId, group, instance);
		}
		catch (Exception e) {
			rethrowRuntimeException(e);
		}

接下来我们来到