Integrate Seata and ShardingSphere

[terrymanu]

ShardingSphere is an open-source ecosystem consisted of a set of distributed database middleware solutions, including 2 independent products, Sharding-JDBC, Sharding-Proxy.

They all provide functions of data sharding, distributed transaction and database orchestration, applicable in a variety of situations such as Java isomorphism, heterogeneous language and cloud native.

ShardingSphere are very glad to integrate Seata as a kind of distributed transaction implementation.

It has already create issue to discuss more details, we can discuss how to integration them better.

[zhangthen]

Look forward to it.

[lingcoder]

Great work!!!Look forward

[cherrylzhao]

hi, all
we have implemented SeataATShardingTransactionManager in this way.

you can get more details from our example.

During integration, I have found some issues that need to be done in seata side.

• reset initialized flag & instance when destroy RpcClient. see PR Reset initialized flag & instance while destroy(). split PR #1105 #1162
• batch remove undo_log SQL is wrong
  it have been resolved in develop branch.
• rollback cannot executed normally.
  it seems undo data validate logic in dev branch is wrong.
• consider about adding a SPI for SQL-Recovery to avoid parsing SQL twice between Seata and ShardingSphere.

I prefer to contribute PRs for that.

[cherrylzhao]

@wuzunqian ShardingSphere have provided transaction api for integrating other transaction, transaction type can changed dynamically in runtime, also you can config DataSourceProxy directly in your application.

[jyizheng]

I am interested in this issue. What it the status of it?

[terrymanu]

This issue is finished, and ShardingSphere has already provide a example. Please try to use in your application if somebody interested.

FYI: https://github.com/apache/incubator-shardingsphere-example/tree/dev/sharding-jdbc-example/transaction-example/transaction-base-seata-raw-jdbc-example

I will close this issue if test enough.