ShardingSphere5.0自定义分布式ID生成器

继承KeyGenerateAlgorithm

public class RedisKeyGenerateAlgorithm implements KeyGenerateAlgorithm {
    @Override
    public Comparable<?> generateKey() {
        RedisTemplate redisTemplate = RestTemplateReadyListener.getRedisTemplateHolder().getRedisTemplate();
        String currentDateTime = DateFormatUtil.getCurrentDateTime("yyyyMMdd");
        Long id = 1L;
        if (!redisTemplate.hasKey("user-id:gen" + ":" + currentDateTime)) {
            redisTemplate.opsForValue().set("user-id:gen" + ":" + currentDateTime, 1);
        } else {
            id = redisTemplate.opsForValue().increment("user-id:gen" + ":" + currentDateTime);
        }
        String format = String.format("%03d", id);

        return currentDateTime + format;
    }

    @Override
    public void init() {
    }

    /**
     * 生成名称
     * @return
     */
    @Override
    public String getType() {
        return "USER_ID_GEN";
    }
}

SPI配置：src/main/resources/META-INF/services/org.apache.shardingsphere.sharding.spi.ShardingAlgorithm

com.example.user.sharding.UserIdSharding

配置生效：

spring:
  config:
    activate:
      on-profile: prod
  shardingsphere:
    datasource:
      names: master,slave
      master:
        type: com.alibaba.druid.pool.DruidDataSource
        driver-class-name: com.mysql.cj.jdbc.Driver
        url: jdbc:mysql://asus:3306/auth_db?characterEncoding=UTF-8&serverTimezone=Asia/Shanghai&autoReconnect=true&failOverReadOnly=false&zeroDateTimeBehavior=convertToNull&useSSL=false
        username: auth_user
        password: zxc521cxzPass!
      slave:
        type: com.alibaba.druid.pool.DruidDataSource  # 数据库配置，配置属性名 不同连接池，连接名不一样。根据数据库连接池DataSource来配置
        driver-class-name: com.mysql.cj.jdbc.Driver
        url: jdbc:mysql://dell:3306/auth_db?characterEncoding=UTF-8&serverTimezone=Asia/Shanghai&autoReconnect=true&failOverReadOnly=false&zeroDateTimeBehavior=convertToNull&useSSL=false
        username: auth_user
        password: zxc521cxzPass!
    props:
      sql-show: true
    rules:
      readwrite-splitting:
        load-balancers:
          roundRobin:
            type: ROUND_ROBIN #从库路由算法，ROUND_ROBIN：轮询，RANDOM：随机
        data-sources:
          read-write_0:
            #自动发现数据源名称（配置动态读写分离规则显示）,库中不配置则读写分离不生效，不配置则为静态分离，可以动态扩容。
            #只支持MySQL的自动发现，可以拓展成根据配置进行动态扩容?
            #auto_aware_data_source_name
            load-balancer-name: roundRobin #轮询算法
            read-data-source-names: slave #读库
            write-data-source-name: master #写库
      sharding:
        tables:
          users:
            table-strategy:
              standard:
                sharding-algorithm-name: table-inline
                sharding-column: user_id
            actual-data-nodes: read-write_0.users_$->{0..1}  #read-write_0 为读写分离的逻辑表明
            keyGenerateStrategy:
              column: user_id
              key-generator-name: user-id-gen
        sharding-algorithms:
          table-inline:
            type: USER_ID
            props:
              sharding-count: 2
        key-generators:
          user-id-gen:
            type: USER_ID_GEN
  redis:
    password: 123456
    port: 6379