阿飞Javaer,转载请注明原创出处,谢谢!
源码图解
根据源码图解可知,sharding-jdbc-orchestration模块中创建数据源有两种方式:工厂类和spring;且有两种数据源类型:OrchestrationShardingDataSource和OrchestrationMasterSlaveDataSource;
- 左边是OrchestrationShardingDataSource类型数据源创建,配置信息持久化以及监听&刷新过程;右边是OrchestrationMasterSlaveDataSource类型数据源创建,配置信息持久化以及监听&刷新过程;
- 工厂类方式通过OrchestrationShardingDataSourceFactory或者OrchestrationMasterSlaveDataSourceFactory创建;
- spring方式通过解析xml配置文件创建(可以参考OrchestrationShardingNamespaceTest测试用例);
- 得到数据源后,调用OrchestrationFacade.init()方法;在该init()方法中持久化配置信息到注册中心中;并创建监听器;
由图可知,两种类型数据源的处理大同小异,本篇文章只分析OrchestrationShardingDataSource这种类型的数据源;
源码分析
接下来通过工厂类创建OrchestrationShardingDataSource类型数据源源码剖析orchestration的实现原理;
1.创建数据源
通过测试用例YamlOrchestrationShardingIntegrateTest可知,创建数据源的代码为OrchestrationShardingDataSourceFactory.createDataSource(yamlFile);这段代码的实现如下所示:
@NoArgsConstructor(access = AccessLevel.PRIVATE)
public final class OrchestrationShardingDataSourceFactory {
public static DataSource createDataSource(
final Map<String, DataSource> dataSourceMap, final ShardingRuleConfiguration shardingRuleConfig,
final Map<String, Object> configMap, final Properties props,
final OrchestrationConfiguration orchestrationConfig) throws SQLException {
// step3.1 创建OrchestrationShardingDataSource数据源
OrchestrationShardingDataSource result = new OrchestrationShardingDataSource(dataSourceMap, shardingRuleConfig, configMap, props, orchestrationConfig);
// step3.2 初始化(这里是sharding-jdb orchestration编排治理的核心)
result.init();
return result;
}
public static DataSource createDataSource(final File yamlFile) throws SQLException, IOException {
// step1. 解析yaml文件得到YamlOrchestrationShardingRuleConfiguration
YamlOrchestrationShardingRuleConfiguration config = unmarshal(yamlFile);
// step2. 得到分库分表规则配置,即根据yaml文件中shardingRule节点信息得到的分库分表规则配置
YamlShardingRuleConfiguration shardingRuleConfig = config.getShardingRule();
// step3. 调用上面的方法创建数据源
return createDataSource(config.getDataSources(), shardingRuleConfig.getShardingRuleConfiguration(),
shardingRuleConfig.getConfigMap(), shardingRuleConfig.getProps(), config.getOrchestration().getOrchestrationConfiguration());
}