I think it's a quick different story, as Skywalking agent doesn't invoke the SQL execution.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Apr 26, 2019 at 6:47 PM Sheng Wu <[email protected]> wrote: > > Please be advised, SkyWalking and seata integration are ongoing too. > > https://github.com/seata/seata/issues/714 > > SkyWalking agent even will be binding in Seata TC binary release. > > As shardingsphere pmc are developing SkyWalking plugin too. Please be > careful, don't make the conflict. > > zhaojun <[email protected]>于2019年4月26日 周五下午6:41写道： > > > Hi, all > > > > currently, we have integrated with saga using graph based engine in > > shardingsphere[1] > > it need us to collect all participated actual SQL, then submit to saga > > actuator in commit/rollback phase. > > if application crashed before invoking saga actuator, undo log of branch > > transaction SQL will not be saved, > > so recovery thread will not be executed correctly. > > > > it's better that encapsulating every actual SQL as a saga task in > > shardingsphere side, > > then submit to saga actuator realtime instead of batch processing all the > > SQLs at commit/rollback phase. > > this architecture will make the boundary more clear between shardingsphre > > and saga, currently we have done some additional works for integrating saga. > > > > any thought? > > > > [1]: > > https://github.com/sharding-sphere/shardingsphere-spi-impl/tree/master/sharding-transaction-spi-impl/sharding-transaction-base-spi-impl/sharding-transaction-base-saga > > < > > https://github.com/sharding-sphere/shardingsphere-spi-impl/tree/master/sharding-transaction-spi-impl/sharding-transaction-base-spi-impl/sharding-transaction-base-saga > > > > > > > > > > > ------------------ > > Zhao Jun > > Apache Sharding-Sphere & ServiceComb > > > > -- > Sheng Wu > SkyWalking, Shardingsphere and Zipkin
