ShardingSphere + Mysql，實現分庫分表、讀寫分離，并整合 SpringBoot

軟件版本

Docker：26.1.3

Mysql：8.4.0

ShardingSphere：5.5.0

分庫分表

1.Docker創建兩個Mysql

services:
  mysql:
    image: mysql:8.4.0
    ports:
      - "3306:3306"
    environment:
      MYSQL_ROOT_PASSWORD: abc123
    volumes:
      - ./data:/var/lib/mysql
      - ./config:/etc/mysql/conf.d
    restart: always

2.兩個Mysql創建測試庫 demo 并導入表

-- demo.t_address definition

CREATE TABLE `t_address` (
  `user_id` bigint NOT NULL AUTO_INCREMENT,
  `name` varchar(100) NOT NULL,
  PRIMARY KEY (`user_id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;


-- demo.t_order_0 definition

CREATE TABLE `t_order_0` (
  `order_id` bigint NOT NULL,
  `user_id` bigint NOT NULL,
  `name` varchar(100) NOT NULL,
  PRIMARY KEY (`order_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;


-- demo.t_order_item_0 definition

CREATE TABLE `t_order_item_0` (
  `order_item_id` bigint NOT NULL,
  `order_id` bigint NOT NULL,
  `user_id` bigint NOT NULL,
  `name` varchar(100) NOT NULL,
  PRIMARY KEY (`order_item_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;


-- demo.t_order_1 definition

CREATE TABLE `t_order_1` (
  `order_id` bigint NOT NULL,
  `user_id` bigint NOT NULL,
  `name` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
  PRIMARY KEY (`order_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;


-- demo.t_order_item_1 definition

CREATE TABLE `t_order_item_1` (
  `order_item_id` bigint NOT NULL,
  `order_id` bigint NOT NULL,
  `user_id` bigint NOT NULL,
  `name` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
  PRIMARY KEY (`order_item_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;

3.Docker 編寫 docker-compose.yml 文件

services:
  shardingsphere:
    image: apache/shardingsphere-proxy:5.5.0
    ports:
      - "3307:3307"
    volumes:
      - ./conf:/opt/shardingsphere-proxy/conf
      - ./ext-lib:/opt/shardingsphere-proxy/ext-lib
    restart: always

4.導入Mysql驅動

請下載 mysql-connector-java-5.1.49.jar 或者 mysql-connector-java-8.0.11.jar，并將其放入 ext-lib 目錄。

5.導入分庫分表配置到 conf/database-sharding.yaml

databaseName: demo

dataSources:
  ds_0:
    url: jdbc:mysql://192.168.1.111:3306/demo?allowPublicKeyRetrieval=true
    username: root
    password: abc123
    connectionTimeoutMilliseconds: 30000
    idleTimeoutMilliseconds: 60000
    maxLifetimeMilliseconds: 1800000
    maxPoolSize: 50
    minPoolSize: 1
  ds_1:
    url: jdbc:mysql://192.168.1.112:3306/demo?allowPublicKeyRetrieval=true
    username: root
    password: abc123
    connectionTimeoutMilliseconds: 30000
    idleTimeoutMilliseconds: 60000
    maxLifetimeMilliseconds: 1800000
    maxPoolSize: 50
    minPoolSize: 1

rules:
  - !SHARDING
    # 分片配置
    tables:
      # 邏輯表名
      t_order:
        # 數據源
        actualDataNodes: ds_${0..1}.t_order_${0..1}
        # 分庫策略，下面默認分庫策略替代
        # databaseStrategy:
        #   standard:
        #     shardingColumn: user_id
        #     shardingAlgorithmName: database_inline
        # 分表策略
        tableStrategy:
          standard:
            # 分片列
            shardingColumn: order_id
            # 分片算法
            shardingAlgorithmName: t_order_inline
        # 主鍵生成策略
        keyGenerateStrategy:
          # 主鍵列
          column: order_id
          # 主鍵生成算法
          keyGeneratorName: snowflake
      # 第二個邏輯表名，配置方式如上
      t_order_item:
        actualDataNodes: ds_${0..1}.t_order_item_${0..1}
        tableStrategy:
          standard:
            shardingColumn: order_id
            shardingAlgorithmName: t_order_item_inline
        keyGenerateStrategy:
          column: order_item_id
          keyGeneratorName: snowflake
    # 綁定表
    bindingTables:
      - t_order,t_order_item
    # 默認分庫策略
    defaultDatabaseStrategy:
      standard:
        shardingColumn: user_id
        shardingAlgorithmName: database_inline
    # 默認分表策略
    defaultTableStrategy:
      none:

    # 定義分片算法
    shardingAlgorithms:
      # 算法名
      database_inline:
        # 算法類型
        type: INLINE
        # 算法屬性
        props:
          algorithm-expression: ds_${user_id % 2}
          allow-range-query-with-inline-sharding: true
      t_order_inline:
        type: INLINE
        props:
          algorithm-expression: t_order_${order_id % 2}
          allow-range-query-with-inline-sharding: true
      t_order_item_inline:
        type: INLINE
        props:
          algorithm-expression: t_order_item_${order_id % 2}
          allow-range-query-with-inline-sharding: true

    # 定義主鍵生成算法
    keyGenerators:
      # 算法名
      snowflake:
        # 算法類型
        type: SNOWFLAKE

  - !BROADCAST
    # 廣播表配置
    tables:
      - t_address

6.啟動 ShardingSphere-Proxy 即可完成

默認URL：jdbc:mysql://127.0.0.1:3307/demo

默認端口：3307

默認賬號：root

默認密碼：root

可以直接像連接普通Mysql數據庫一樣使用了。

讀寫分離

1.先準備兩個Mysql服務器，并配好主從復制

Mysql 8.4.0 結合 Docker 搭建GTID主從復制，以及傳統主從復制 - Yfeil - 博客園 (cnblogs.com)

2.Docker 編寫 docker-compose.yml 文件

services:
  shardingsphere:
    image: apache/shardingsphere-proxy:5.5.0
    ports:
      - "3307:3307"
    volumes:
      - ./conf:/opt/shardingsphere-proxy/conf
      - ./ext-lib:/opt/shardingsphere-proxy/ext-lib
    restart: always

3.導入Mysql驅動

請下載 mysql-connector-java-5.1.49.jar 或者 mysql-connector-java-8.0.11.jar，并將其放入 ext-lib 目錄。

4.導入讀寫分離配置到 conf/database-readwrite-splitting.yaml

databaseName: demo

dataSources:
  write_ds:
    url: jdbc:mysql://192.168.1.113:3306/demo?allowPublicKeyRetrieval=true
    username: root
    password: abc123
    connectionTimeoutMilliseconds: 30000
    idleTimeoutMilliseconds: 60000
    maxLifetimeMilliseconds: 1800000
    maxPoolSize: 50
    minPoolSize: 1
  read_ds:
    url: jdbc:mysql://192.168.1.114:3306/demo?allowPublicKeyRetrieval=true
    username: root
    password: abc123
    connectionTimeoutMilliseconds: 30000
    idleTimeoutMilliseconds: 60000
    maxLifetimeMilliseconds: 1800000
    maxPoolSize: 50
    minPoolSize: 1

rules:
  - !READWRITE_SPLITTING
    dataSources:
      # 邏輯數據源名
      readwrite_ds:
        # 寫庫數據源
        writeDataSourceName: write_ds
        # 讀庫數據源
        readDataSourceNames:
          - read_ds
        loadBalancerName: random
    
    # 定義負載均衡算法
    loadBalancers:
      # 算法名
      random:
        #算法類型
        type: RANDOM

  - !SINGLE
    # 單表規則
    tables:
      - readwrite_ds.*

5.啟動 ShardingSphere-Proxy 即可完成

默認URL：jdbc:mysql://127.0.0.1:3307/demo

默認端口：3307

默認賬號：root

默認密碼：root

可以直接像連接普通Mysql數據庫一樣使用了。

JDBC 整合 SpringBoot 2.x

ShardingSphere-JDBC 對 SpringBoot 3.x 支持的不好，硬要使用先去官網看看注意事項。

這里只演示分庫分表的整合，讀寫分離同理。

1.引入依賴

<dependency>
    <groupId>org.apache.shardingsphere</groupId>
    <artifactId>shardingsphere-jdbc</artifactId>
    <version>5.5.0</version>
    <exclusions>
        <exclusion>
            <groupId>org.apache.shardingsphere</groupId>
            <artifactId>shardingsphere-test-util</artifactId>
        </exclusion>
    </exclusions>
</dependency>
<dependency>
    <groupId>org.yaml</groupId>
    <artifactId>snakeyaml</artifactId>
    <version>2.2</version>
</dependency>
<dependency>
    <groupId>com.mysql</groupId>
    <artifactId>mysql-connector-j</artifactId>
    <scope>runtime</scope>
</dependency>

2.添加配置

# 配置 DataSource Driver
spring.datasource.driver-class-name=org.apache.shardingsphere.driver.ShardingSphereDriver
# 指定 YAML 配置文件
spring.datasource.url=jdbc:shardingsphere:classpath:database-sharding.yaml

3.創建 src/main/resources/database-sharding.yaml

rules 配置和之前一樣，主要區別在于 dataSources 下的配置變了。

dataSources:
  ds_0:
    dataSourceClassName: com.zaxxer.hikari.HikariDataSource
    driverClassName: com.mysql.jdbc.Driver
    jdbcUrl: jdbc:mysql://192.168.1.111:3306/demo?allowPublicKeyRetrieval=true
    username: root
    password: abc123
  ds_1:
    dataSourceClassName: com.zaxxer.hikari.HikariDataSource
    driverClassName: com.mysql.jdbc.Driver
    jdbcUrl: jdbc:mysql://192.168.1.112:3306/demo?allowPublicKeyRetrieval=true
    username: root
    password: abc123

rules:
  - !SHARDING
    # 分片配置
    tables:
      # 邏輯表名
      t_order:
        # 數據源
        actualDataNodes: ds_${0..1}.t_order_${0..1}
        # 分庫策略，下面默認分庫策略替代
        # databaseStrategy:
        #   standard:
        #     shardingColumn: user_id
        #     shardingAlgorithmName: database_inline
        # 分表策略
        tableStrategy:
          standard:
            # 分片列
            shardingColumn: order_id
            # 分片算法
            shardingAlgorithmName: t_order_inline
        # 主鍵生成策略
        keyGenerateStrategy:
          # 主鍵列
          column: order_id
          # 主鍵生成算法
          keyGeneratorName: snowflake
      # 第二個邏輯表名，配置方式如上
      t_order_item:
        actualDataNodes: ds_${0..1}.t_order_item_${0..1}
        tableStrategy:
          standard:
            shardingColumn: order_id
            shardingAlgorithmName: t_order_item_inline
        keyGenerateStrategy:
          column: order_item_id
          keyGeneratorName: snowflake
    # 綁定表
    bindingTables:
      - t_order,t_order_item
    # 默認分庫策略
    defaultDatabaseStrategy:
      standard:
        shardingColumn: user_id
        shardingAlgorithmName: database_inline
    # 默認分表策略
    defaultTableStrategy:
      none:

    # 定義分片算法
    shardingAlgorithms:
      # 算法名
      database_inline:
        # 算法類型
        type: INLINE
        # 算法屬性
        props:
          algorithm-expression: ds_${user_id % 2}
          allow-range-query-with-inline-sharding: true
      t_order_inline:
        type: INLINE
        props:
          algorithm-expression: t_order_${order_id % 2}
          allow-range-query-with-inline-sharding: true
      t_order_item_inline:
        type: INLINE
        props:
          algorithm-expression: t_order_item_${order_id % 2}
          allow-range-query-with-inline-sharding: true

    # 定義主鍵生成算法
    keyGenerators:
      # 算法名
      snowflake:
        # 算法類型
        type: SNOWFLAKE

  - !BROADCAST
    # 廣播表配置
    tables:
      - t_address

4.完成

平時咋操作數據庫現在也一樣，也可以引入 Mybatis，可以無縫連接。

參考

數據分片 :: ShardingSphere (apache.org)

讀寫分離 :: ShardingSphere (apache.org)

分片算法 :: ShardingSphere (apache.org)

負載均衡算法 :: ShardingSphere (apache.org)

使用限制 :: ShardingSphere (apache.org)

posted @ 2024-06-07 23:02 Yfeil 閱讀(1183) 評論(0) 收藏舉報

刷新頁面返回頂部