Seata source code analysis: a preliminary official example

    Quick start Let's start with a microservice example. The official example uses the AT mode in seata distributed transaction, that is, the example is based on: Based on a relational database that supports local ACID transactions.Java application, accessing database through JDBC.. Use case Business logic for users to purchase goods. T ...

Added by daiwa on Tue, 08 Mar 2022 20:26:34 +0200

Seata-XA schema principles

1 XA pattern example Example reference: on github seata-sample Business code level and xa are identical, just replace the database proxy level with DataSourceProxyXA, more, refer to the example. 2 Architecture Note: This image is from the seata website. 3 Source Analysis 3.1 TM Open Global Transactions This process is the same as AT mode ...

Added by jesseledwards on Tue, 08 Feb 2022 20:34:14 +0200

Production and deployment of docker image of distributed transaction seat server

Seata is an open source distributed transaction solution, which is committed to providing high-performance and easy-to-use distributed transaction services. It provides users with several different transaction modes such as AT, TCC, SAGA and XA. There are three main roles in Seata. TM and RM are integrated with the business system as Seata's cl ...

Added by sb on Mon, 10 Jan 2022 02:23:54 +0200

Consistency challenge: data consistency solution under microservice architecture

CAP principle and BASE theorem CAP principle CAP is the acronym combination of Consistency, Availability and Partition tolerance. It is a priority for designers of all distributed systems before design. CAP principle Consistency C means that after the update operation is successful, the data of all nodes are completely consiste ...

Added by JMair on Mon, 20 Dec 2021 17:44:30 +0200

Distributed transaction - Seata - AT getting started

With the growth of data volume, the performance of a single database can no longer meet the requirements. Therefore, the method of database and table division was born to improve the access performance of RMDB. The problem caused by database division is that transactions cannot be controlled through a single DB connection (multiple database ...

Added by RightNow21 on Mon, 08 Nov 2021 01:16:59 +0200