Spring Boot整合MyBatis实战与性能优化指南

1. Spring Boot与MyBatis整合实战指南在企业级Java开发中Spring Boot和MyBatis的组合已经成为主流的持久层解决方案。这套技术栈完美结合了Spring Boot的快速开发特性和MyBatis的灵活SQL控制能力特别适合需要精细控制SQL同时又追求开发效率的项目场景。我曾在多个电商和金融项目中采用这种架构实测下来比纯JPA方案性能提升30%以上特别是在复杂查询和批量操作场景下优势更为明显。下面就从实战角度分享这套技术栈的核心配置技巧和最佳实践。1.1 技术选型背景解析Spring Boot的自动配置机制与MyBatis的Mapper代理模式存在天然的互补性。Spring Boot 2.7.x MyBatis 3.5.x是目前最稳定的组合新项目建议直接采用Spring Boot 3.x MyBatis 3.5.10的组合。这里有个版本兼容性要点Spring Boot 3.x需要Java 17而MyBatis 3.5.9开始才完全支持Java 17的特性。重要提示生产环境务必锁定mybatis-spring-boot-starter的版本号不同版本间的事务管理行为可能有细微差异1.2 基础环境搭建创建项目时推荐使用Spring Initializr勾选Spring Web (用于RESTful接口)MyBatis Framework对应数据库驱动(MySQL/PostgreSQL等)对于Maven项目关键依赖应包含dependency groupIdorg.mybatis.spring.boot/groupId artifactIdmybatis-spring-boot-starter/artifactId version3.0.2/version /dependency dependency groupIdcom.mysql/groupId artifactIdmysql-connector-j/artifactId scoperuntime/scope /dependency2. 核心配置详解2.1 数据源配置最佳实践application.yml中建议采用HikariCP连接池配置spring: datasource: url: jdbc:mysql://localhost:3306/demo?useSSLfalseserverTimezoneUTC username: root password: 123456 hikari: maximum-pool-size: 20 minimum-idle: 5 connection-timeout: 30000 idle-timeout: 600000 max-lifetime: 1800000MyBatis专属配置项需要特别注意mybatis: mapper-locations: classpath:mapper/*.xml type-aliases-package: com.example.demo.entity configuration: map-underscore-to-camel-case: true default-fetch-size: 100 default-statement-timeout: 302.2 动态SQL实战技巧MyBatis最强大的特性之一就是动态SQL这里分享几个高频使用技巧批量插入优化insert idbatchInsert useGeneratedKeystrue keyPropertyid INSERT INTO user(name,age) VALUES foreach collectionlist itemitem separator, (#{item.name}, #{item.age}) /foreach /insert多条件查询select idselectByCondition resultTypeUser SELECT * FROM user where if testname ! null and name ! AND name LIKE CONCAT(%,#{name},%) /if if testminAge ! null AND age #{minAge} /if choose when testorderBy name ORDER BY name /when otherwise ORDER BY id /otherwise /choose /where /select3. 高级特性深度应用3.1 注解与XML混合开发模式虽然注解方式简洁但复杂SQL仍推荐XML方式。两者可以混合使用Mapper public interface UserMapper { Select(SELECT * FROM user WHERE id #{id}) User selectById(Param(id) Long id); // XML中实现 ListUser selectByComplexCondition(UserQuery query); }3.2 二级缓存与Redis集成启用二级缓存并整合Redis的配置步骤添加Redis依赖dependency groupIdorg.springframework.boot/groupId artifactIdspring-boot-starter-data-redis/artifactId /dependency实现Redis缓存Configuration public class MyBatisRedisConfig { Bean public Cache mybatisRedisCache(RedisConnectionFactory factory) { RedisCacheConfiguration config RedisCacheConfiguration.defaultCacheConfig() .serializeValuesWith(RedisSerializationContext.SerializationPair .fromSerializer(new GenericJackson2JsonRedisSerializer())); return RedisCache.builder(mybatisCache) .cacheDefaults(config) .transactionAware() .build(); } }Mapper层应用缓存CacheNamespace(implementation MyBatisRedisCache.class, eviction MyBatisRedisCache.class) public interface ProductMapper { Options(useCache true) Select(SELECT * FROM product WHERE id #{id}) Product selectById(Long id); }4. 性能优化与监控4.1 SQL性能分析集成p6spy监控真实SQLspring: datasource: driver-class-name: com.p6spy.engine.spy.P6SpyDriver url: jdbc:p6spy:mysql://localhost:3306/demo配置spy.propertiesmodule.logcom.p6spy.engine.logging.P6LogFactory appendercom.p6spy.engine.spy.appender.Slf4JLogger logMessageFormatcom.p6spy.engine.spy.appender.CustomLineFormat customLogMessageFormat%(currentTime)|%(executionTime)|%(category)|%(sql)4.2 MyBatis-Plus扩展应用对于需要更多自动化功能的场景可以引入MyBatis-PlusService public class UserServiceImpl extends ServiceImplUserMapper, User implements UserService { public PageUser queryByPage(PageParam param) { LambdaQueryWrapperUser wrapper Wrappers.lambdaQuery(); wrapper.like(StringUtils.isNotBlank(param.getKeyword()), User::getName, param.getKeyword()) .ge(param.getMinAge() ! null, User::getAge, param.getMinAge()); return baseMapper.selectPage(new Page(param.getPage(), param.getSize()), wrapper); } }5. 生产环境注意事项SQL注入防护严禁使用${}拼接SQL动态表名场景使用Provider方式SelectProvider(type UserSqlProvider.class, method selectByTable) ListUser selectByTable(Param(tableName) String tableName);事务管理要点Transactional(rollbackFor Exception.class, propagation Propagation.REQUIRED) public void businessMethod() { // 跨Mapper操作 }连接泄露排查 在application.yml中添加logging: level: org.springframework.jdbc.datasource.DataSourceTransactionManager: DEBUG分页插件优化Bean public MybatisPlusInterceptor mybatisPlusInterceptor() { MybatisPlusInterceptor interceptor new MybatisPlusInterceptor(); interceptor.addInnerInterceptor(new PaginationInnerInterceptor(DbType.MYSQL){ Override protected void optimizeCount(IPage? page, JdbcUtils jdbcUtils) { // 自定义count优化 } }); return interceptor; }这套技术栈在日订单量百万级的电商系统中表现稳定通过合理的缓存策略和SQL优化平均查询响应时间可以控制在50ms以内。特别是在处理复杂报表查询时直接编写优化后的SQL比JPA的Criteria API性能高出5-8倍。