BASE #

A paper published in 2008 first mentioned that BASE transaction advocates the use of eventual consistency instead of consistency to improve concurrency of transaction processing.

TCC and Saga are two regular implementations. They use reverse operation implemented by developers themselves to ensure the eventual consistency when data rollback. SEATA implements SQL reverse operation automatically, so that BASE transaction can be used without the intervention of developers.

Apache ShardingSphere integrates SEATA as solution of BASE transaction.