ShardingSphere-Proxy5搭建使用过程分析

rules:
 - !AUTHORITY
   users: # 配置连接shardingsphere-proxy的用户
     - root@127.0.0.1:root
     - sharding@:sharding
   provider: # 授权模式
     type: ALL_PERMITTED # 不用授权，获取所有权限

# windows
# 指定端口号和配置文件目录, 默认端口为3307
bin/start.bat ${proxy_port} ${proxy_conf_directory}

# 拉取镜像
docker pull apache/shardingsphere-proxy

# 启动临时容器
docker run -d --name tmp --entrypoint=bash apache/shardingsphere-proxy:5.2.0

# 配置文件拷贝
docker cp tmp:/opt/shardingsphere-proxy/conf /mnt/data/shardingsphere-proxy/
#删除临时容器
docker rm tmp

# 注意镜像的扩张依赖需要放在ext-lib目录，不能直接覆盖lib目录
docker run --name shardingsphere-proxy -d -v /mnt/data/shardingsphere-proxy/conf:/opt/shardingsphere-proxy/conf -v /mnt/data/shardingsphere-proxy/ext-lib:/opt/shardingsphere-proxy/ext-lib -e PORT=3307 -p 33307:3307 apache/shardingsphere-proxy:5.2.0

docker run --name shardingsphere-proxy -d -v /mnt/data/shardingsphere-proxy/conf:/opt/shardingsphere-proxy/conf -e PORT=3307 -p 33307:3307 apache/shardingsphere-proxy:5.2.0

databaseName: sharding_db ##逻辑库。配置多个逻辑库时需要创建其他的配置文件，并且配置文件格式需为config-sharding***.yaml

dataSources: ## 数据源，连接真实物理库，注意物理库必须有相应的库存在，负责proxy无法启动。
ds_0:
url: jdbc:mysql://127.0.0.1:13307/demo_ds_0?serverTimezone=UTC&useSSL=false
username: root
password: sunday
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
ds_1:
url: jdbc:mysql://127.0.0.1:3306/demo_ds_1?serverTimezone=UTC&useSSL=false
username: root
password: sunday
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1

databaseName: sharding_db

dataSources: ## 数据源，连接真实物理库，注意物理库必须有相应的库存在，负责proxy无法启动。
ds_0:
url: jdbc:mysql://127.0.0.1:13307/demo_ds_0?serverTimezone=UTC&useSSL=false
username: root
password: sunday
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
ds_1:
url: jdbc:mysql://127.0.0.1:3306/demo_ds_1?serverTimezone=UTC&useSSL=false
username: root
password: sunday
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: alg_mod # 算法名称
tableStrategy: # 分表规则
standard:
shardingColumn: order_no
shardingAlgorithmName: alg_hash_mod # 算法名称，具体使用哪一种算法下面会根据算法名称配置
keyGenerateStrategy: # 主键生成规则
column: id
keyGeneratorName: snowflake
# bindingTables: # 绑定表。对于相同分片算法的表，设置绑定，避免相互关联时产生笛卡尔关联
# broadcastTables: # 广播表

keyGenerators: # 主键生成规则配置
snowflake:
type: SNOWFLAKE

shardingAlgorithms: # 分片算法配置，根据上面的算法名称配置算法的类型和算法接收的参数
alg_mod:
type: MOD
props:
sharding-count: 2
alg_hash_mod:
type: HASH_MOD
props:
sharding-count: 2

CREATE TABLE `t_order` (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`order_no` varchar(30) DEFAULT NULL,
`user_id` bigint(20) DEFAULT NULL,
`amount` decimal(10,2) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=779468255126355969 DEFAULT CHARSET=utf8mb4;

INSERT INTO `sharding_db`.`t_order`(`id`, `order_no`, `user_id`, `amount`) VALUES (779468213359476737, '22', 22, 22.00);
INSERT INTO `sharding_db`.`t_order`(`id`, `order_no`, `user_id`, `amount`) VALUES (779468285585391617, '44', 44, 44.00);
INSERT INTO `sharding_db`.`t_order`(`id`, `order_no`, `user_id`, `amount`) VALUES (779468168534949888, '11', 11, 11.00);
INSERT INTO `sharding_db`.`t_order`(`id`, `order_no`, `user_id`, `amount`) VALUES (779468255126355968, '33', 33, 33.00);