Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/apache/incubator-seata
:fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution.
https://github.com/apache/incubator-seata
at consistency distributed-transaction microservice saga tcc xa
Last synced: 3 days ago
JSON representation
:fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution.
- Host: GitHub
- URL: https://github.com/apache/incubator-seata
- Owner: apache
- License: apache-2.0
- Created: 2018-12-28T08:37:22.000Z (almost 6 years ago)
- Default Branch: 2.x
- Last Pushed: 2024-10-29T14:44:24.000Z (about 1 month ago)
- Last Synced: 2024-10-29T21:14:21.404Z (about 1 month ago)
- Topics: at, consistency, distributed-transaction, microservice, saga, tcc, xa
- Language: Java
- Homepage: https://seata.apache.org/
- Size: 23.9 MB
- Stars: 25,306
- Watchers: 847
- Forks: 8,778
- Open Issues: 819
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
- stars - apache/incubator-seata - to-use, high-performance, open source distributed transaction solution. (HarmonyOS / Windows Manager)
- my-awesome - apache/incubator-seata - transaction,microservice,saga,tcc,xa pushed_at:2024-12 star:25.4k fork:8.8k :fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution. (Java)
README
# Seata: Simple Extensible Autonomous Transaction Architecture
[](https://github.com/apache/incubator-seata/actions)
[](https://codecov.io/gh/apache/incubator-seata)
[](https://www.apache.org/licenses/LICENSE-2.0.html)
[](https://central.sonatype.com/search?q=org.apache.seata%3Aseata-all)
## 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.
Things have changed in a microservices architecture. The 3 modules mentioned above are designed to be 3 services on top of 3 different data sources ([Pattern: Database per service](http://microservices.io/patterns/data/database-per-service.html)). Data consistency within every single service is naturally guaranteed by the local transaction.
**But how about the whole business logic scope?**
### How Seata do?
Seata is just a solution to the problem mentioned above.
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**.
There are three roles in Seata Framework:
- **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.
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 registers 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.
For more details about principle and design, please go to [Seata wiki page](https://github.com/apache/incubator-seata/wiki).
### History
##### Alibaba
- **TXC**: Taobao Transaction Constructor. Alibaba middleware team started this project since 2014 to meet the distributed transaction problems 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 started the open source project Fescar based on TXC/GTS since 2019 to work closely with the community in the future.
##### 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 .
##### 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 renamed to Seata.
## Maven dependency
Depending on the scenario, choose one of the two dependencies: `org.apache.seata:seata-all` or `org.apache.seata:seata-spring-boot-starter`.
```xml
2.2.0
org.apache.seata
seata-all
${seata.version}
org.apache.seata
seata-spring-boot-starter
${seata.version}
```
## Quick Start
[Quick Start](https://seata.apache.org/zh-cn/docs/ops/deploy-guide-beginner)
## Documentation
You can view the full documentation from Seata Official Website: [Seata Website page](https://seata.apache.org/zh-cn/docs/overview/what-is-seata).
## Reporting bugs
Please follow the [template](./.github/ISSUE_TEMPLATE/BUG_REPORT.md) for reporting any issues.
## Security
Please do not use our public issue tracker but refer to our [security policy](./SECURITY.md)
## Contributing
Contributors are welcomed to join the Seata project. Please check [CONTRIBUTING](./CONTRIBUTING.md) and [CONTRIBUTING-CN](./CONTRIBUTING_CN.md) about how to contribute to this project.
## Contact
* Mailing list:
* [email protected] , for dev/user discussion. [subscribe](mailto:[email protected]), [unsubscribe](mailto:[email protected]), [archive](https://lists.apache.org/[email protected])
* Online chat:
| Dingtalk group | Wechat official account | QQ group | Wechat assistant |
|:---------------------------------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------------------:|
| 
| 
| 
| 
|
## Seata ecosystem
* [Seata Website](https://github.com/apache/incubator-seata.github.io) - Seata official website
* [Seata GoLang](https://github.com/apache/incubator-seata-go) - Seata GoLang client and server
* [Seata Samples](https://github.com/apache/incubator-seata-samples) - Samples for Seata
* [Seata GoLang Samples](https://github.com/apache/incubator-seata-go-samples) - Samples for Seata GoLang
* [Seata K8s](https://github.com/apache/incubator-seata-k8s) - Seata integration with k8s
* [Seata CLI](https://github.com/apache/incubator-seata-ctl) - CLI tool for Seata
## Contributors
This project exists thanks to all the people who contribute. [[Contributors](https://github.com/apache/incubator-seata/graphs/contributors)].
## License
Seata is under the Apache 2.0 license. See the [LICENSE](https://github.com/apache/incubator-seata/blob/master/LICENSE) file for details.
## Who is using
These are only part of the companies using Seata, for reference only. If you are using Seata, please [add your company
here](https://github.com/apache/incubator-seata/issues/1246) to tell us your scenario to make Seata better.
