The system architecture is like this: dubbo + zookeeper + + mybatis + mysql, redis had not to tackle the problem of distributed transactions to solve now,
Under the condition of without affecting the existing structure, using Seata better or use the TX - Lcn better ah?

bosses

CodePudding user response:

The architecture does not affect what TCC, don't consider the transaction message, seata support XA, TX - Lcn appeared to have 3 PCS submission, XA to lock resources, poor performance, don't know the TX - Lcn performance

CodePudding user response:

Both use again, that a simple, slightly invasive smaller?

CodePudding user response:

Seata also support TCC, website: http://seata.io/zh-cn/docs/dev/mode/tcc-mode.html

Github1 thousands of more than 7000 star,

Tx - LCN on gitee, only more than 800 star, market application estimate was small:
https://gitee.com/wangliang1991/tx-lcn