Google Git
Sign in
apache / incubator-seata / f4469eaa2aba11ab7337be3c4da124c03b873687
commitf4469eaa2aba11ab7337be3c4da124c03b873687[log] [tgz]
authorjimin <slievrly@163.com>Tue Apr 30 21:46:41 2019 +0800
committerxingfudeshi <xingfudeshi@vip.qq.com>Tue Apr 30 21:46:41 2019 +0800
treedc896ddea8c83b7dcae2790f810482fefdd8dc97
parentba9f4ab5356d5632886636213c2715e36c1f8ca6 [diff]
version:change version to 0.6.0-SNAPSHOT (#958)
3 files changed
tree: dc896ddea8c83b7dcae2790f810482fefdd8dc97
  1. .github/
  2. .mvn/
  3. common/
  4. config/
  5. core/
  6. discovery/
  7. distribution/
  8. integration/
  9. rm/
  10. rm-datasource/
  11. server/
  12. spring/
  13. style/
  14. tcc/
  15. test/
  16. tm/
  17. .gitignore
  18. .travis.yml
  19. CHANGELOG.md
  20. changeVersion.sh
  21. CODE_OF_CONDUCT.md
  22. CONTRIBUTING.md
  23. LICENSE
  24. mvnw
  25. mvnw.cmd
  26. NOTICE.md
  27. pom.xml
  28. README.md
README.md

Seata: Simple Extensible Autonomous Transaction Architecture

Build Status codecov license maven

What is Seata?

A distributed transaction solution with high performance and ease of use for microservices architecture.

Distributed Transaction Problem in Microservices

Let's imagine a traditional monolithic application. Its business is built up with 3 modules. They use a single local data source.

Naturally, data consistency will be guaranteed by the local transaction.

Monolithic App

Things have changed in microservices architecture. The 3 modules mentioned above are designed to be 3 services on top of 3 different data sources (Pattern: Database per service). Data consistency within every single service is naturally guaranteed by the local transaction.

But how about the whole business logic scope?

Microservices Problem

How Seata do?

Seata is just a solution to the problem mentioned above.

Seata solution

Firstly, how to define a Distributed Transaction?

We say, a Distributed Transaction is a Global Transaction which is made up with a batch of Branch Transaction, and normally Branch Transaction is just Local Transaction.

Global & Branch

There are 3 basic components in Seata:

  • Transaction Coordinator(TC): Maintain status of global and branch transactions, drive the global commit or rollback.
  • Transaction Manager(TM): Define the scope of global transaction: begin a global transaction, commit or rollback a global transaction.
  • Resource Manager(RM): Manage resources that branch transactions working on, talk to TC for registering branch transactions and reporting status of branch transactions, and drive the branch transaction commit or rollback.

Model

A typical lifecycle of Seata managed distributed transaction:

  1. TM asks TC to begin a new global transaction. TC generates an XID representing the global transaction.
  2. XID is propagated through microservices' invoke chain.
  3. RM register local transaction as a branch of the corresponding global transaction of XID to TC.
  4. TM asks TC for committing or rollbacking the corresponding global transaction of XID.
  5. TC drives all branch transactions under the corresponding global transaction of XID to finish branch committing or rollbacking.

Typical Process

For more details about principle and design, please go to Seata wiki page.

History

Ant Financial

  • XTS: Extended Transaction Service. Ant Financial middleware team developed the distributed transaction middleware since 2007, which is widely used in Ant Financial and solves the problems of data consistency across databases and services.

  • DTX: Distributed Transaction Extended. Since 2013, XTS has been published on the Ant Financial Cloud, with the name of DTX .

Alibaba
  • TXC: Taobao Transaction Constructor. Alibaba middleware team start this project since 2014 to meet distributed transaction problem caused by application architecture change from monolithic to microservices.
  • GTS: Global Transaction Service. TXC as an Aliyun middleware product with new name GTS was published since 2016.
  • Fescar: we start the open source project Fescar based on TXC/GTS since 2019 to work closely with the community in the future.
Seata Community
  • Seata :Simple Extensible Autonomous Transaction Architecture. Ant Financial joins Fescar, which make it to be a more neutral and open community for distributed transaction，and Fescar be rename to Seata.

Maven dependency

<seata.version>0.5.1</seata.version>

<dependency>
    <groupId>io.seata</groupId>
    <artifactId>seata-spring</artifactId>
    <version>${seata.version}</version>
</dependency>

<!--dependency for Apache Dubbo-->
<dependency>
    <groupId>io.seata</groupId>
    <artifactId>seata-dubbo</artifactId>
    <version>${seata.version}</version>
</dependency>

<!--dependency for Alibaba Dubbo-->
<dependency>
    <groupId>io.seata</groupId>
    <artifactId>seata-dubbo-alibaba</artifactId>
    <version>${seata.version}</version>
</dependency>

Quick Start

Quick Start

Documentation

You can view the full documentation from the wiki: Seata wiki page.

Reporting bugs

Please follow the template for reporting any issues.

Contributing

Contributors are welcomed to join the FEATS project. Please check CONTRIBUTING about how to contribute to this project.

Contact

Dingtalk

Seata ecosystem

Contributors

This project exists thanks to all the people who contribute. [Contributors].

License

Seata is under the Apache 2.0 license. See the LICENSE file for details.