Spring Boot项目实战ShardingSphere 4.1.1与达梦数据库8.1.3分表配置全流程在当今数据驱动的商业环境中数据库性能优化已成为开发者必须面对的挑战。当单表数据量突破千万级时查询响应速度明显下降传统解决方案如索引优化、硬件升级往往收效有限。这时分表技术便成为解决这一痛点的有效方案。本文将详细介绍如何在Spring Boot项目中使用ShardingSphere 4.1.1为达梦数据库8.1.3实现高效的分表配置。1. 环境准备与依赖配置在开始分表配置前我们需要确保开发环境准备就绪。首先创建一个标准的Spring Boot项目推荐使用Spring Initializr进行项目初始化选择Java 8和Spring Boot 2.7.x版本。核心依赖配置如下dependencies dependency groupIdorg.springframework.boot/groupId artifactIdspring-boot-starter/artifactId /dependency dependency groupIdcom.dameng/groupId artifactIdDmJdbcDriver18/artifactId version8.1.3.140/version /dependency dependency groupIdorg.apache.shardingsphere/groupId artifactIdsharding-jdbc-spring-boot-starter/artifactId version4.1.1/version /dependency dependency groupIdcom.alibaba/groupId artifactIddruid/artifactId version1.2.6/version /dependency dependency groupIdcom.baomidou/groupId artifactIdmybatis-plus-boot-starter/artifactId version3.4.2/version /dependency /dependencies提示ShardingSphere 4.1.1版本与达梦8.1.3的兼容性经过充分验证建议不要随意升级版本以避免潜在兼容性问题。数据库表结构设计是分表的基础。假设我们有一个商品表需要进行分表可以创建以下表结构CREATE TABLE TEST.GOODS_1 ( GID BIGINT, GNAME VARCHAR(50), USER_ID BIGINT, GSTATUS VARCHAR(50) ) STORAGE(ON MAIN, CLUSTERBTR); CREATE TABLE TEST.GOODS_2 ( GID BIGINT, GNAME VARCHAR(50), USER_ID BIGINT, GSTATUS VARCHAR(50) ) STORAGE(ON MAIN, CLUSTERBTR);2. ShardingSphere核心配置详解ShardingSphere的配置是整个分表功能的核心。我们需要在application.properties文件中进行详细配置# MyBatis日志配置 mybatis-plus.configuration.log-implorg.apache.ibatis.logging.stdout.StdOutImpl # 允许Bean定义覆盖 spring.main.allow-bean-definition-overridingtrue # 显示SQL日志 spring.shardingsphere.props.sql.showtrue # 数据源配置 spring.shardingsphere.datasource.namesg1 spring.shardingsphere.datasource.g1.typecom.alibaba.druid.pool.DruidDataSource spring.shardingsphere.datasource.g1.driver-class-namedm.jdbc.driver.DmDriver spring.shardingsphere.datasource.g1.urljdbc:dm://192.168.1.10:5236/TEST spring.shardingsphere.datasource.g1.usernameSYSDBA spring.shardingsphere.datasource.g1.password******** # 分表策略配置 spring.shardingsphere.sharding.tables.goods.actual-data-nodesg1.goods_$-{1..2} spring.shardingsphere.sharding.tables.goods.key-generator.columngid spring.shardingsphere.sharding.tables.goods.key-generator.typeSNOWFLAKE spring.shardingsphere.sharding.tables.goods.table-strategy.inline.sharding-columngid spring.shardingsphere.sharding.tables.goods.table-strategy.inline.algorithm-expressiongoods_$-{gid % 2 1}配置项解析actual-data-nodes指定实际的数据节点这里表示goods表将被分散到goods_1和goods_2两个物理表中key-generator配置分布式ID生成策略使用雪花算法生成唯一IDtable-strategy定义分表策略这里采用基于gid的取模分片算法注意达梦数据库的表名和字段名区分大小写配置时需特别注意与数据库中的实际命名保持一致。3. 业务代码实现有了基础配置后我们需要实现业务代码来验证分表功能。首先定义商品实体类Data public class Goods { private Long gid; private String gname; private Long userId; private String gstatus; }接着创建Mapper接口这里使用MyBatis-Plus简化开发Repository public interface GoodsMapper extends BaseMapperGoods { }为了测试分表效果我们编写测试类SpringBootTest class SharingJdbcTestApplicationTests { Autowired GoodsMapper goodsMapper; Test void testShardingInsert() { for (int i 0; i 10; i) { Goods good new Goods(); good.setGname(商品 i); good.setUserId(100L); good.setGstatus(上架); goodsMapper.insert(good); } } Test void testShardingQuery() { QueryWrapperGoods queryWrapper new QueryWrapper(); queryWrapper.eq(gid, 1354449944638820361L); Goods good goodsMapper.selectOne(queryWrapper); System.out.println(good); } }4. 分片策略深度解析与优化ShardingSphere提供了多种分片策略我们需要根据业务特点选择最合适的方案。以下是几种常见策略的对比策略类型适用场景优点缺点标准分片明确的分片键配置简单性能好需要业务有明确分片键复合分片多维度分片支持复杂分片逻辑配置复杂Hint分片无分片键灵活性强需要手动指定路由行表达式简单分片配置简洁功能有限对于商品表的分片我们采用了行表达式策略spring.shardingsphere.sharding.tables.goods.table-strategy.inline.algorithm-expressiongoods_$-{gid % 2 1}这个表达式表示根据gid字段的值进行取模运算模数为2因为我们有2个分表结果加1是为了匹配表编号goods_1和goods_2如果需要更复杂的分片逻辑可以实现自定义分片算法public class CustomTableShardingAlgorithm implements PreciseShardingAlgorithmLong { Override public String doSharding(CollectionString tableNames, PreciseShardingValueLong shardingValue) { // 自定义分片逻辑 return goods_ (shardingValue.getValue() % 2 1); } }然后在配置中引用这个自定义算法spring.shardingsphere.sharding.tables.goods.table-strategy.standard.sharding-columngid spring.shardingsphere.sharding.tables.goods.table-strategy.standard.precise-algorithm-class-namecom.example.CustomTableShardingAlgorithm5. 性能监控与问题排查实施分表后监控系统性能至关重要。ShardingSphere提供了丰富的监控指标和日志功能。启用SQL日志可以帮助我们理解ShardingSphere的实际执行过程spring.shardingsphere.props.sql.showtrue典型日志输出示例2025-03-26 13:50:49.247 INFO 7072 --- [main] ShardingSphere-SQL : Logic SQL: INSERT INTO goods (gid, gname, user_id, gstatus) VALUES (?, ?, ?, ?) 2025-03-26 13:50:49.247 INFO 7072 --- [main] ShardingSphere-SQL : Actual SQL: g1 ::: INSERT INTO goods_1 (gid, gname, user_id, gstatus) VALUES (?, ?, ?, ?) ::: [1354452535414263808, 小米手机, 100, 已发布]常见问题及解决方案分片键选择不当症状数据分布不均匀某些分片负载过高解决重新评估分片键选择离散度高的字段跨分片查询性能差症状涉及多个分片的查询响应慢解决优化查询条件尽量带上分片键考虑使用绑定表分布式事务问题症状跨分片操作数据不一致解决启用ShardingSphere的分布式事务支持达梦数据库特有的注意事项达梦对SQL标准的实现有细微差异复杂SQL可能需要调整达梦的JDBC URL格式为jdbc:dm://host:port/DATABASE达梦默认端口是5236而非常见的3306或54326. 高级特性与最佳实践掌握了基础分表配置后我们可以进一步探索ShardingSphere的高级功能。读写分离集成 ShardingSphere可以同时配置分表和读写分离# 主库配置 spring.shardingsphere.datasource.master.typecom.alibaba.druid.pool.DruidDataSource spring.shardingsphere.datasource.master.driver-class-namedm.jdbc.driver.DmDriver spring.shardingsphere.datasource.master.urljdbc:dm://master-host:5236/TEST # 从库配置 spring.shardingsphere.datasource.slave0.typecom.alibaba.druid.pool.DruidDataSource spring.shardingsphere.datasource.slave0.driver-class-namedm.jdbc.driver.DmDriver spring.shardingsphere.datasource.slave0.urljdbc:dm://slave-host:5236/TEST # 读写分离规则 spring.shardingsphere.sharding.master-slave-rules.ds0.master-data-source-namemaster spring.shardingsphere.sharding.master-slave-rules.ds0.slave-data-source-namesslave0分布式主键优化 默认的雪花算法可能存在性能瓶颈可以考虑使用达梦数据库自增序列需调整分片策略实现自定义分布式ID生成器使用Leaf等分布式ID服务分库分表结合 对于超大规模数据可以同时使用分库和分表# 多数据源配置 spring.shardingsphere.datasource.namesds0,ds1 # 分库策略 spring.shardingsphere.sharding.tables.goods.database-strategy.inline.sharding-columnuser_id spring.shardingsphere.sharding.tables.goods.database-strategy.inline.algorithm-expressionds$-{user_id % 2} # 分表策略 spring.shardingsphere.sharding.tables.goods.actual-data-nodesds$-{0..1}.goods_$-{0..1} spring.shardingsphere.sharding.tables.goods.table-strategy.inline.sharding-columngid spring.shardingsphere.sharding.tables.goods.table-strategy.inline.algorithm-expressiongoods_$-{gid % 2}实际项目中我们发现在达梦数据库上使用ShardingSphere时连接池配置对性能影响很大。推荐使用Druid连接池并优化以下参数# 连接池配置 spring.shardingsphere.datasource.g1.initialSize5 spring.shardingsphere.datasource.g1.minIdle5 spring.shardingsphere.datasource.g1.maxActive20 spring.shardingsphere.datasource.g1.maxWait60000 spring.shardingsphere.datasource.g1.timeBetweenEvictionRunsMillis60000 spring.shardingsphere.datasource.g1.minEvictableIdleTimeMillis300000