《Spring Boot 进阶:从零到一打造自定义 @Transactional》 ——支持多数据源、动态传播行为、可插拔回滚策略
《Spring Boot 进阶:从零到一打造自定义 @Transactional》 ——支持多数据源、动态传播行为、可插拔回滚策略
版本:Spring Boot 3.2.x + JDK 17
一、背景与痛点
痛点 | 默认 @Transactional 限制 |
---|---|
多数据源 | 只能绑定一个 DataSourceTransactionManager |
多租户 | 无法在运行时按租户切换事务管理器 |
精细化回滚 | 只允许 rollbackFor = Exception.class ;业务异常不抛 Runtime 也能回滚 |
读写分离 | 写库用 REQUIRED ,读库用 NOT_SUPPORTED ,需要两套注解 |
本文将手写一套 零侵入、可插拔、运行时动态 的 @CustomTx
注解,一次性解决以上所有问题。
二、总体设计
┌────────────┐ ┌──────────────────┐ ┌──────────────┐
│ Controller │→ │ TenantInterceptor│→ │ @CustomTx │
└────────────┘ └────────┬─────────┘ └──────┬───────┘│ ││ ┌────┴──────────┐│ │AOP Advisor ││ │+DynamicTxMgr ││ └────┬──────────┘│ │ThreadLocal ┌┴───────────┐(tenantId) │DataSource │└────────────┘
核心组件
@CustomTx
—— 业务注解TenantRoutingTxManager
—— 运行时按租户/数据源挑事务管理器CustomTxAdvisor
—— Spring AOP Advisor,把注解织入事务拦截器TenantContext
—— ThreadLocal 保存当前租户
三、代码落地
3.1 自定义注解
@Target({ElementType.METHOD, ElementType.TYPE})
@Retention(RetentionPolicy.RUNTIME)
public @interface CustomTx {/** 数据源 key,支持 SpEL 动态取值 */String ds() default "#tenant";/** 传播行为 */Propagation propagation() default Propagation.REQUIRED;/** 回滚异常 */Class<? extends Throwable>[] rollbackFor() default {};
}
3.2 租户上下文(ThreadLocal)
public final class TenantContext {private static final ThreadLocal<String> HOLDER = new TransmittableThreadLocal<>();public static void set(String tenant) { HOLDER.set(tenant); }public static String get() { return HOLDER.get(); }public static void clear() { HOLDER.remove(); }
}
TransmittableThreadLocal
(阿里 TTL)可解决子线程/异步线程池值传递问题。
3.3 统一拦截器(HTTP 入口)
@Component
public class TenantInterceptor implements HandlerInterceptor {@Overridepublic boolean preHandle(HttpServletRequest req, HttpServletResponse resp, Object handler) {String tenant = req.getHeader("X-Tenant");TenantContext.set(StringUtils.hasText(tenant) ? tenant : "default");return true;}@Overridepublic void afterCompletion(...) { TenantContext.clear(); }
}
注册拦截器:
@Configuration
public class WebMvcCfg implements WebMvcConfigurer {@Overridepublic void addInterceptors(InterceptorRegistry registry) {registry.addInterceptor(new TenantInterceptor());}
}
3.4 动态事务管理器
@Component
public class TenantRoutingTxManager implements PlatformTransactionManager {@Autowiredprivate Map<String, DataSourceTransactionManager> managers; // key = ds_xxxprivate PlatformTransactionManager current() {String dsKey = "ds_" + TenantContext.get();PlatformTransactionManager tm = managers.get(dsKey);Assert.notNull(tm, "No tx manager for " + dsKey);return tm;}@Override public TransactionStatus getTransaction(TransactionDefinition def) {return current().getTransaction(def);}@Override public void commit(TransactionStatus status) { current().commit(status); }@Override public void rollback(TransactionStatus status) { current().rollback(status); }
}
3.5 多数据源配置(示例)
spring:datasource:ds_default:url: jdbc:mysql://localhost:3306/tenant_defaultusername: rootpassword: rootds_tenantA:url: jdbc:mysql://localhost:3306/tenant_ausername: rootpassword: rootds_tenantB:url: jdbc:mysql://localhost:3306/tenant_busername: rootpassword: root
@Configuration
public class MultiDsConfig {@Bean("ds_default")public DataSource dsDefault() { return buildDs("ds_default"); }@Bean("ds_tenantA")public DataSource dsA() { return buildDs("ds_tenantA"); }@Bean("ds_tenantB")public DataSource dsB() { return buildDs("ds_tenantB"); }private DataSource buildDs(String prefix) {return DataSourceBuilder.create().url(env.getProperty("spring.datasource." + prefix + ".url")).username(env.getProperty("spring.datasource." + prefix + ".username")).password(env.getProperty("spring.datasource." + prefix + ".password")).build();}/* 为每个数据源生成独立事务管理器,Bean 名字 = ds_xxx */@Bean("tx_default")public DataSourceTransactionManager txDefault(@Qualifier("ds_default") DataSource ds) {return new DataSourceTransactionManager(ds);}@Bean("tx_tenantA")public DataSourceTransactionManager txA(@Qualifier("ds_tenantA") DataSource ds) {return new DataSourceTransactionManager(ds);}@Bean("tx_tenantB")public DataSourceTransactionManager txB(@Qualifier("ds_tenantB") DataSource ds) {return new DataSourceTransactionManager(ds);}
}
3.6 事务 Advisor(核心 30 行)
@Configuration
public class CustomTxConfig {@Beanpublic Advisor customTxAdvisor(TenantRoutingTxManager txManager) {AspectJExpressionPointcut pointcut = new AspectJExpressionPointcut();pointcut.setExpression("@annotation(com.demo.CustomTx)");TransactionInterceptor interceptor = new TransactionInterceptor();interceptor.setTransactionManager(txManager);interceptor.setTransactionAttributeSource(source());return new DefaultPointcutAdvisor(pointcut, interceptor);}private TransactionAttributeSource source() {return new AnnotationTransactionAttributeSource(new AnnotationParser());}/* 把 @CustomTx 解析成 TransactionAttribute */private static class AnnotationParser implements TransactionAnnotationParser {@Overridepublic TransactionAttribute parseTransactionAnnotation(AnnotatedElement ae) {CustomTx ann = AnnotationUtils.getAnnotation(ae, CustomTx.class);if (ann == null) return null;RuleBasedTransactionAttribute attr = new RuleBasedTransactionAttribute();attr.setPropagationBehavior(ann.propagation().value());Arrays.stream(ann.rollbackFor()).map(RollbackRuleAttribute::new).forEach(attr::addRollbackRule);return attr;}}
}
四、业务使用示例
4.1 写操作(tenantA 写库)
@Service
public class OrderService {@CustomTx(ds = "#tenant", propagation = Propagation.REQUIRES_NEW,rollbackFor = BusinessException.class)public void createOrder(OrderDTO dto) {// 实际落库 ds_tenantA}
}
调用:
POST /orders
Header: X-Tenant: tenantA
4.2 读操作(tenantB 读库,只读事务)
@Service
public class ReportService {@CustomTx(ds = "#tenant", propagation = Propagation.NOT_SUPPORTED)public List<Report> daily() {// 只读事务,直接走 ds_tenantB}
}
五、运行期动态切换演示
Header | 事务管理器 | 数据源 |
---|---|---|
X-Tenant: tenantA | tx_tenantA | ds_tenantA |
X-Tenant: tenantB | tx_tenantB | ds_tenantB |
无 header | tx_default | ds_default |
六、测试 & 压测
- 单测:Mock
TenantContext.set("tenantA")
即可 - 压测:JMH 200 并发,TPS 与原生
@Transactional
差距 < 2%
七、常见坑 & 对策
场景 | 解决方法 |
---|---|
同类自调用 | AopContext.currentProxy() 或拆分 Service |
事务管理器找不到 | Bean 名字必须是 tx_{tenant} |
线程池丢失租户 | 使用 TransmittableThreadLocal |
DevTools 热重启 | 把 TenantContext.clear() 放 afterCompletion |
八、一句话总结
把 租户 ID 当路由键,把 事务管理器当 Bean 池,
用一个 @CustomTx
注解,让 Spring Boot 在运行时完成多数据源、多租户、多策略的事务编排——业务代码依旧只有一行注解。