# Seata **Repository Path**: billion_lines_of_code/Seata ## Basic Information - **Project Name**: Seata - **Description**: Seata 是一款开源的分布式事务解决方案,提供高性能和简单易用的分布式事务服务 - **Primary Language**: Java - **License**: Apache-2.0 - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 93 - **Created**: 2020-06-04 - **Last Updated**: 2020-12-19 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Seata: Simple Extensible Autonomous Transaction Architecture [![Build Status](https://travis-ci.org/seata/seata.svg?branch=develop)](https://travis-ci.org/seata/seata) [![codecov](https://codecov.io/gh/seata/seata/branch/develop/graph/badge.svg)](https://codecov.io/gh/seata/seata) [![license](https://img.shields.io/github/license/seata/seata.svg)](https://www.apache.org/licenses/LICENSE-2.0.html) [![maven](https://img.shields.io/maven-central/v/io.seata/seata-parent.svg)](https://search.maven.org/search?q=io.seata) [![](https://img.shields.io/twitter/follow/seataio.svg?label=Follow&style=social&logoWidth=0)](https://twitter.com/intent/follow?screen_name=seataio) ## 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](https://cdn.nlark.com/lark/0/2018/png/18862/1545296770244-4cedf37e-9dc6-4fc0-a97f-f4240b9d8640.png) 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](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?** ![Microservices Problem](https://cdn.nlark.com/lark/0/2018/png/18862/1545296781231-4029da9c-8803-43a4-ac2f-6c8b1e2ea448.png) ### How Seata do? Seata is just a solution to the problem mentioned above. ![Seata solution](https://cdn.nlark.com/lark/0/2018/png/18862/1545296791074-3bce7bce-025e-45c3-9386-7b95135dade8.png) 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](https://cdn.nlark.com/lark/0/2018/png/18862/1545015454979-a18e16f6-ed41-44f1-9c7a-bd82c4d5ff99.png) 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](https://cdn.nlark.com/lark/0/2018/png/18862/1545013915286-4a90f0df-5fda-41e1-91e0-2aa3d331c035.png) 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](https://cdn.nlark.com/lark/0/2018/png/18862/1545296917881-26fabeb9-71fa-4f3e-8a7a-fc317d3389f4.png) For more details about principle and design, please go to [Seata wiki page](https://github.com/seata/seata/wiki). ### 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 renamed to Seata. ## Maven dependency ```xml 1.2.0 io.seata seata-all ${seata.version} ``` ## Quick Start [Quick Start](https://github.com/seata/seata/wiki/Quick-Start) ## Documentation You can view the full documentation from the wiki: [Seata wiki page](https://github.com/seata/seata/wiki). ## Reporting bugs Please follow the [template](https://github.com/seata/seata/blob/develop/.github/ISSUE_TEMPLATE/BUG_REPORT.md) for reporting any issues. ## Contributing Contributors are welcomed to join the Seata project. Please check [CONTRIBUTING](./CONTRIBUTING.md) about how to contribute to this project. ## Contact * [Twitter](https://twitter.com/seataio): Follow along for latest Seata news on Twitter. * Mailing list: * dev-seata@googlegroups.com , for dev/user discussion. [subscribe](mailto:dev-seata+subscribe@googlegroups.com), [unsubscribe](mailto:dev-seata+unsubscribe@googlegroups.com), [archive](https://groups.google.com/forum/#!forum/dev-seata) ## Seata ecosystem * [Seata Ecosystem Entry](https://github.com/seata) - A GitHub group `seata` to gather all Seata relevant projects * [Seata Samples](https://github.com/seata/seata-samples) - Samples for Seata * [Seata Docker](https://github.com/seata/seata-docker) - Seata integration with docker * [Seata K8s](https://github.com/seata/seata-k8s) - Seata integration with k8s * [Awesome Seata](https://github.com/seata/awesome-seata) - Seata's slides and video address in meetup * [Seata Website](https://github.com/seata/seata.github.io) - Seata official website ## Contributors This project exists thanks to all the people who contribute. [[Contributors](https://github.com/seata/seata/graphs/contributors)]. ## License Seata is under the Apache 2.0 license. See the [LICENSE](https://github.com/seata/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/seata/seata/issues/1246) to tell us your scenario to make Seata better.
Alibaba Group 蚂蚁金服 阿里云 中航信 中国铁塔 滴滴 联通(浙江) 中国邮政 58集团 太极计算机 政采云 浙江公安厅 特步 中通快递 美的集团 浙江烟草 韵达快递 波司登 凯京科技 点购集团 求是创新健康 TCL 科蓝 康美药业 雁联 学两手 衣二三 悦途出行 睿颐软件 有利网 赛维 安心保险 科达科技 会分期 会找房 全房通 会通教育 享住智慧 兰亮网络 蓝天教育 烟台欣合 阿康健康 新脉远 乾动新能源 路客精品民宿 深圳好尔美 浙大睿医 居然之家 臻善科技 中国支付通 众网小贷 谐云科技 浙江甄品 深圳海豚网 汇通天下 九机网 有好东西 南京智慧盾 数跑科技 拉粉粉 汇通达 财新传媒 易宝支付 维恩贝特 八库 大诚若谷 成都数智索 宿迁民丰农商银行 杭州喜团科技 上海海智在线 丞家(上海)公寓管理 北京超图 深圳易佰 安徽国科新材科 易点生活 商银信支付 钛师傅云 广州力生信息