1、seata是什么
SEATA(Simple Extensible Autonomous Transaction Architecture)
2痘系、seata-demo編譯運(yùn)行
- 編譯seata
從github
下載seata
源碼飒箭,源碼地址https://github.com/seata/seata.git
;
切換到tag v1.4.2最新版本
mvn clean package -Dmaven.test.skip -Prelease-seata
- 編譯seata-samples
從github
下載seata-samples
源碼,源碼地址https://github.com/seata/seata-samples.git
mvn clean package -Dmaven.test.skip
若需要打可執(zhí)行jar包則可進(jìn)到目錄后運(yùn)行
seata\seata-samples\springcloud-eureka-seata>mvn clean package -Dmaven.test.skip -Dlicense.skip spring-boot:repackage
-
運(yùn)行demo
演示使用springcloud-eureka-seata
這個案例米碰,依次啟動以下應(yīng)用按照腳本
seata-samples\springcloud-eureka-seata\all.sql
建好數(shù)據(jù)數(shù)據(jù)庫表,并建好相應(yīng)的用戶购城,依次啟動以下應(yīng)用即可演示
1)吕座、eureka
2)、seata-server 目錄(打包編譯后在目錄\seata\distribution\seata-server-1.4.2\bin中seata-server.bat)
3)瘪板、account
4)吴趴、storage
5)、order
6)侮攀、budiness
訪問curl http://127.0.0.1:8084/purchase/commit
驗證結(jié)果
3锣枝、針對現(xiàn)有spring-boot系統(tǒng)使用seata改造
由于現(xiàn)有系統(tǒng)均由spring-boot開發(fā),并且未對分布式事務(wù)進(jìn)行有效的處理或補(bǔ)償兰英,基于目前對業(yè)務(wù)量撇叁、并發(fā)量的考慮引入seata解決分布式事務(wù)的問題,各個服務(wù)之間的調(diào)用統(tǒng)一使用了Resttemplate實現(xiàn)畦贸;
場景案例
如下單場景中陨闹,訂單服務(wù)(seata-order)調(diào)用了庫存服務(wù)(seata-stock),若扣減庫成功了薄坏,并將成功結(jié)果返回到訂單服務(wù)趋厉,然后訂單服務(wù)因為某些原因保存訂單失敗,此時就應(yīng)該回滾扣減的庫存胶坠;改造方案
涉及到的分布式事務(wù)的場景較多君账,目標(biāo)是以最小的代價完成升級改造,主要涉及幾個點(diǎn):
①引入seata依賴沈善、②增加seata配置乡数、③涉及全局事務(wù)的地方使用@GlobalTransactional、④增加resttemplate攔截器(目的是傳遞全局事務(wù)ID)闻牡、⑤創(chuàng)建undo_log表瞳脓;-
升級改造前示例(使用spring-boot-2.6.4完成模擬)
源代碼https://gitee.com/viturefree/spring-boot-seata-upgrade
對應(yīng)的v1分支,使用時可分別使用curl -X POST http://localhost:8082/order/true
模擬成功或curl -X POST http://localhost:8082/order/false
模擬失敗澈侠,可以看到在有庫存的情況下無論成功或失敗均扣庫存了劫侧,我們期望的是若失敗應(yīng)該回滾返回庫存;改造前的依賴如下
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<dependency>
<groupId>com.alibaba</groupId>
<artifactId>druid-spring-boot-starter</artifactId>
<version>1.2.8</version>
</dependency>
<dependency>
<groupId>org.mariadb.jdbc</groupId>
<artifactId>mariadb-java-client</artifactId>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
部分關(guān)鍵代碼片斷
@Transactional
public void saveSuccess(Order order) throws Exception {
//此處模擬先調(diào)用庫存服務(wù)扣減庫存
useStock();
orderRepository.save(order);
}
@Transactional
public void saveFailure(Order order) throws Exception {
//此處模擬先調(diào)用庫存服務(wù)扣減庫存
useStock();
orderRepository.save(order);
throw new RuntimeException("模擬保存訂單失敗");
}
private void useStock() {
restTemplate.postForObject("http://localhost:8083/stock", "", String.class);
}
------
@Transactional
public void quota() {
int result = stockRepository.update(1);
if(result==0)
throw new RuntimeException("扣減庫存失敗");
log.debug("{}", result);
}
------
//扣減庫存操作返回操作行數(shù),返回0的時候表示扣減失敗了
@Modifying
@Query("update Stock s set s.stock=s.stock-10 where s.id=?1 and s.stock>=10")
int update(int id);
-
升級使用seata解決分布式事務(wù)問題
引入seata依賴包
<dependency>
<groupId>io.seata</groupId>
<artifactId>seata-spring-boot-starter</artifactId>
<version>1.4.2</version>
</dependency>
application.yaml
中增加seata配置(其中有大量配置使用默認(rèn)配置即可),注意www.mnxyz.zeo.com:8091
為seata服務(wù)地址烧栋;
seata:
enabled: true
application-id: ${spring.application.name}
tx-service-group: minxyz-seata-group
service:
vgroup-mapping:
minxyz-seata-group: minxyz
grouplist:
minxyz: www.mnxyz.zeo.com:8091
按seata-order.sql
和seata-stock.sql
分別建好undo_log
表写妥,若已經(jīng)建好忽略;
涉及事務(wù)的訂單服務(wù)增加@GlobalTransactional
注解审姓,即在類OrderService
的方法saveSuccess
和saveFailure
上增加珍特;
此時應(yīng)用可以啟動兩個應(yīng)用進(jìn)行調(diào)用,會發(fā)現(xiàn)沒有效果魔吐,原因是通過RestTemplate
調(diào)用的時候并沒有完成全局事務(wù)ID的跨服務(wù)傳遞扎筒,由于沒有使用spring-cloud,如eureka的實現(xiàn)酬姆,不然就不需要自行實現(xiàn)攔截器處理事務(wù)ID了嗜桌,更新方便快捷遷移;
可以通過在seata-stock
打印請求頭信息發(fā)現(xiàn)沒有傳遞tx_xid參數(shù)
HttpServletRequest request = ((ServletRequestAttributes) RequestContextHolder.getRequestAttributes()).getRequest();
Enumeration<String> headers = request.getHeaderNames();
while (headers.hasMoreElements()) {
String header = headers.nextElement();
log.info("{}={}", header, request.getHeader(header));
}
接下來實現(xiàn)攔截全局事務(wù)ID辞色,在案例中是使用RestTemplate
調(diào)用時需要攔截增加tx_xid
骨宠;
編寫seata-resttemplate-spring-boot-starter
,假定命名為seata-resttemplate
此名字相满,并在seata-order
及seata-stock
中引入此依賴层亿,關(guān)鍵代碼如下
seata-resttemplate-spring-boot-starter 模塊如下
pom.xml >>>>>>
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.minxyz</groupId>
<artifactId>seata-resttemplate-spring-boot-starter</artifactId>
<version>0.0.1</version>
<properties>
<java.version>1.8</java.version>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
<encoding>UTF-8</encoding>
</properties>
<dependencies>
<dependency>
<groupId>io.seata</groupId>
<artifactId>seata-spring-boot-starter</artifactId>
<version>1.4.2</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludes>
<exclude>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
</build>
</project>
spring.factories >>>>>>
org.springframework.boot.autoconfigure.EnableAutoConfiguration=\
com.minxyz.seata.SeataRestTemplateAutoConfiguration
SeataRestTemplateAutoConfiguration >>>>>>
package com.minxyz.seata;
import io.seata.common.util.StringUtils;
import io.seata.core.context.RootContext;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.context.annotation.Configuration;
import org.springframework.http.client.support.HttpRequestWrapper;
import org.springframework.web.client.RestTemplate;
import javax.annotation.PostConstruct;
import java.util.Collection;
import java.util.Iterator;
@Configuration
public class SeataRestTemplateAutoConfiguration {
@Autowired(required = false)
private Collection<RestTemplate> restTemplates;
public SeataRestTemplateAutoConfiguration() {
}
@PostConstruct
public void init() {
if (this.restTemplates != null) {
Iterator<RestTemplate> it = this.restTemplates.iterator();
while (it.hasNext()) {
it.next().getInterceptors().add((request, body, execution) -> {
HttpRequestWrapper requestWrapper = new HttpRequestWrapper(request);
String xid = RootContext.getXID();
if (StringUtils.isNotEmpty(xid)) {
requestWrapper.getHeaders().add(RootContext.KEY_XID, xid);
}
return execution.execute(requestWrapper, body);
});
}
}
}
}
主要目的就是攔截傳遞tx_xid
這個header
參數(shù);
接著在seata-order
和seata-stock
中依賴些starter
<dependencies>
<dependency>
<groupId>com.minxyz</groupId>
<artifactId>seata-resttemplate-spring-boot-starter</artifactId>
<version>0.0.1</version>
</dependency>
</dependencies>
源代碼https://gitee.com/viturefree/spring-boot-seata-upgrade
對應(yīng)的v2分支
4立美、觀察undo_log數(shù)據(jù)
由于undo_log執(zhí)行時會被清除匿又,可增加一個觸發(fā)器觀察執(zhí)行的數(shù)據(jù);
創(chuàng)建undo_log備份表
CREATE TABLE `undo_log_backup` (
`id` bigint(20) NOT NULL,
`branch_id` bigint(20) NOT NULL,
`xid` varchar(100) NOT NULL,
`context` varchar(128) NOT NULL,
`rollback_info` longblob NOT NULL,
`log_status` int(11) NOT NULL,
`log_created` datetime NOT NULL,
`log_modified` datetime NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `ux_undo_log` (`xid`,`branch_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
創(chuàng)建觸發(fā)器將undo_log數(shù)據(jù)備份
CREATE TRIGGER `undo_log_trigger` AFTER INSERT ON `undo_log` FOR EACH ROW begin
insert into undo_log_backup(id,branch_id,xid,context,rollback_info,log_status,log_created,log_modified)
values(new.id,new.branch_id,new.xid,new.context,new.rollback_info,new.log_status,new.log_created,new.log_modified);
end;