国际财务系统基于shardingsphere的数据分片和一主多从实践-凯发app官方网站

#数据源名称
spring.shardingsphere.datasource.names= defaultmaster,ds0,ds1,ds2,ds3,ds4,ds5,ds6,ds7,ds8,ds9,ds10,ds11,ds12,ds13,ds14,ds15,ds16,ds17,ds18,ds19,ds20,ds21,ds22,ds23,ds24,ds25,ds26,ds27,ds28,ds29,ds30,ds31,slave0,slave1
#未配置分片规则的表将通过默认数据源定位，注意值必须配置为读写分离的分组名称groupname1
spring.shardingsphere.sharding.default-data-source-name=groupname1
#主库
spring.shardingsphere.datasource.defaultmaster.jdbc-url=jdbc:mysql:
spring.shardingsphere.datasource.defaultmaster.type= com.zaxxer.hikari.hikaridatasource
spring.shardingsphere.datasource.defaultmaster.driver-class-name= com.mysql.jdbc.driver
#分库ds0
spring.shardingsphere.datasource.ds0.jdbc-url=jdbc:mysql:
spring.shardingsphere.datasource.ds0.type= com.zaxxer.hikari.hikaridatasource
spring.shardingsphere.datasource.ds0.driver-class-name= com.mysql.jdbc.driver
#从库slave0
spring.shardingsphere.datasource.slave0.jdbc-url=jdbc:mysql:
spring.shardingsphere.datasource.slave0.type= com.zaxxer.hikari.hikaridatasource
spring.shardingsphere.datasource.slave0.driver-class-name= com.mysql.jdbc.driver
#从库slave1
spring.shardingsphere.datasource.slave1.jdbc-url=jdbc:mysql:
spring.shardingsphere.datasource.slave1.type= com.zaxxer.hikari.hikaridatasource
spring.shardingsphere.datasource.slave1.driver-class-name= com.mysql.jdbc.driver
#由数据源名   表名组成，以小数点分隔。多个表以逗号分隔，支持inline表达式。缺省表示使用已知数据源与逻辑表名称生成数据节点，用于广播表（即每个库中都需要一个同样的表用于关联查询，多为字典表）或只分库不分表且所有库的表结构完全一致的情况
spring.shardingsphere.sharding.tables.incident_ar.actual-data-nodes=ds$->{0..127}.incident_ar
#行表达式分片策略 分库策略，缺省表示使用默认分库策略
spring.shardingsphere.sharding.tables.incident_ar.database-strategy.inline.sharding-column= dept_no
#分片算法行表达式，需符合groovy语法
spring.shardingsphere.sharding.tables.incident_ar.database-strategy.inline.algorithm-expression=ds$->{dept_no.touppercase().hashcode().abs() % 128}
#读写分离配置
spring.shardingsphere.sharding.master-slave-rules.groupname1.master-data-source-name=defaultmaster
spring.shardingsphere.sharding.master-slave-rules.groupname1.slave-data-source-names[0]=slave0
spring.shardingsphere.sharding.master-slave-rules.groupname1.slave-data-source-names[1]=slave1
spring.shardingsphere.sharding.master-slave-rules.groupname1.load-balance-algorithm-type=round_robin

import lombok.getter;
import lombok.requiredargsconstructor;
import lombok.setter;
import org.apache.shardingsphere.spi.masterslave.masterslaveloadbalancealgorithm;
import org.springframework.stereotype.component;
import java.util.list;
import java.util.properties;
@component
@getter
@setter
@requiredargsconstructor
public final class loadalgorithm implements masterslaveloadbalancealgorithm {
    private properties properties = new properties();
    @override
    public string gettype() {return "loadbalance";}
    @override
    public string getdatasource(final string name, final string masterdatasourcename, final list slavedatasourcenames) {
        //自己的负载均衡规则
        return slavedatasourcenames.get(0);

@documented
@target({elementtype.method})
@retention(retentionpolicy.runtime)
public @interface seekmaster {
}
import lombok.extern.slf4j.slf4j;
import org.apache.shardingsphere.api.hint.hintmanager;
import org.aspectj.lang.proceedingjoinpoint;
import org.aspectj.lang.annotation.around;
import org.aspectj.lang.annotation.aspect;
import org.springframework.stereotype.component;
/**
 * shardingsphere >读写分离自定义注解>用于实现读写分离时>需要强制读主库的场景（注解实现类）
 *
 * @author zhangguangzhi1
 **/
@slf4j
@aspect
@component
public class seekmasterannotation {
    
    @around("@annotation(seekmaster)")
    public object dointerceptor(proceedingjoinpoint joinpoint, seekmaster seekmaster) throws throwable {
        object object = null;
        throwable t = null;
        try {
            hintmanager.getinstance().setmasterrouteonly();
            log.info("强制查询主库");
            object = joinpoint.proceed();
        } catch (throwable throwable) {
            t = throwable;
        } finally {
            hintmanager.clear();
            if (t != null) {
                throw t;
            }
        }
        return object;

create table if not exists `undo_log`
(
  `id`            bigint(20)   not null auto_increment comment 'increment id',
  `branch_id`     bigint(20)   not null comment 'branch transaction id',
  `xid`           varchar(100) not null comment 'global transaction id',
  `context`       varchar(128) not null comment 'undo_log context,such as serialization',
  `rollback_info` longblob     not null comment 'rollback info',
  `log_status`    int(11)      not null comment '0:normal status,1:defense status',
  `log_created`   datetime     not null comment 'create datetime',
  `log_modified`  datetime     not null comment 'modify datetime',
  primary key (`id`),
  unique key `ux_undo_log` (`xid`, `branch_id`)
) engine = innodb
  auto_increment = 1
  default charset = utf8 comment ='at transaction mode undo table';

client {
    application.id = example    ## 应用唯一id
    transaction.service.group = my_test_tx_group   ## 所属事务组
}