Does Shardingsphere-proxy currently support integration with Seata?

[26903651]

Does Shardingsphere-proxy currently support integration with Seata? The official documentation only seems to have information on integrating Shardingsphere-jdbc with Seata. If it is possible to integrate Shardingsphere-proxy with Seata, are there any relevant documents or examples available?

[terrymanu]

It supports the early Seata version, but no time to integrate the newest version for now.

[26903651]

It supports the early Seata version, but no time to integrate the newest version for now.

Could you please tell me which version of Seata is compatible with ShardingSphere-Proxy? Is there any relevant documentation?

[terrymanu]

FYI: https://github.com/search?q=repo%3Aapache%2Fshardingsphere+seata+language%3A%22Maven+POM%22&type=code&l=Maven+POM

[26903651]

I'm sorry, after entering this link, I did not find any examples on how to integrate ShardingSphere-Proxy with Seata. Could you tell me more please?

[linghengqian]

@26903651

• What I can tell you clearly is that a lot of unit tests for shardingsphere's seata integration are not actually in shardingsphere's master branch because Seata Multi-Client Optimization incubator-seata#6614 is not resolved.

1. Shardingsphere jdbc's seata integration and seata client 2.2.0 can be used under both HotSpot VM and GraalVM Native Image.

2. Shardingsphere proxy's seata integration and seata client 2.2.0 can be used under HotSpot VM, but have not been tested under shardingsphere proxy native under GraalVM Native Image. The reason why the relevant unit tests are not in shardingsphere's master branch is that Seata Client should allow dynamic monitoring of changes in service.default.grouplist incubator-seata#7039 is not resolved.

• In order to support GraalVM Native Image, all ShardingSphere support for Seata Client 1.x has been abandoned. See Improve GraalVM Reachability Metadata and corresponding nativeTest related unit tests #29052 , https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/special-api/transaction/seata/ and 跨越 MySQL 边界 -- GraalVM Native Image 下 ShardingSphere JDBC 的 Seata AT 集成 https://www.yuque.com/linghengqian/meve2v/es8d3a8a18odao7x .
• Back to the current issue, there is actually not much to do except updating the documentation.
• Of course, in order to further resolve the dependency conflicts of Seata Client, I tend to change the seata client used by shardingsphere for testing from 2.1.0 to 2.2.0 . We all know that the Docker Image of Seata 2.2.0 currently has 593 CVEs, which means we need to speed up. See Add support for org.apache.seata:seata-all:2.1.0 oracle/graalvm-reachability-metadata#542 (comment) .