search

apache / shardingsphere

Distributed SQL transaction & query engine for data sharding, scaling, encryption, and more - on any database.
Apache License 2.0
19.83k stars 6.71k forks source link

Regarding Distributed Transaction #26754

Open zhong2312 opened 1 year ago

zhong2312 commented 1 year ago

image I believe the instructions in this document are not very accurate. In the context of shardingsphere and single-service cross-database transactions, the XA mode is expected to have better performance than Seata's AT mode. This is because, in the absence of cross-service scenarios, the XA mode does not require long waits for transaction execution; it only needs to handle commit and rollback operations. On the other hand, the AT mode requires querying and writing data copies before and after the write operations, as well as writing undo logs, which clearly consumes more time.

The AT mode outperforms the XA mode only in scenarios involving cross-service transactions. This is because cross-service transactions result in the inability to process the business logic of each transaction branch before a unified transaction commit, leading to longer waiting times.

terrymanu commented 1 year ago

What is the content url?

terrymanu commented 1 year ago

Could you submit a pull request to fix the doc?

zhong2312 commented 1 year ago

What is the content url?

https://shardingsphere.apache.org/document/current/cn/features/transaction/ image

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.