tag | 57dc12cf8a95e797abd144df97463b43a3350335 | |
---|---|---|
tagger | Luky116Liuyuecai <luky116@126.com> | Sat Jul 30 18:47:54 2022 +0800 |
object | 6df29f519284f9299847463df6df3a55dcc02036 |
the first relase
commit | 6df29f519284f9299847463df6df3a55dcc02036 | [log] [tgz] |
---|---|---|
author | Yuecai Liu <38887641+luky116@users.noreply.github.com> | Sat Jul 30 18:35:35 2022 +0800 |
committer | GitHub <noreply@github.com> | Sat Jul 30 18:35:35 2022 +0800 |
tree | 75ac23d369aa0dfde2bc7c60b3a05df1965e34bb | |
parent | 2569cf79bd873c4530d5845024dc6136ae1cb748 [diff] |
doc: add release 0.1.0 changes note (#169) doc: add release 0.0.1-rc1 changes note
Seata is a very mature distributed transaction framework, and is the de facto standard platform for distributed transaction technology in the Java field. Seata-go is the implementation version of go language in Seata multilingual ecosystem, which realizes the interoperability between Java and Go, so that Go developers can also use seata-go to realize distributed transactions. Please visit the official website of Seata to view the quick start and documentation.
The principle of seata-go is consistent with that of Seata-java, which is composed of TM, RM and TC. The functions of TC reuse Java, and the functions of TM and RM will be aligned with Seata-java later. The overall process is as follows:
Start the seata-server service with the docker file under the sample/dockercomposer folder
cd sample/dockercompose docker-compose -f docker-compose.yml up -d seata-server
Just execute the main function under samples/ in the root directory
Seata-go is currently in the construction stage. Welcome colleagues in the industry to join the group and work with us to promote the construction of seata-go! If you want to contribute code to seata-go, you can refer to the code contribution Specification document to understand the specifications of the community, or you can join our community DingTalk group: 33069364 and communicate together!
Seata-go uses Apache license version 2.0. Please refer to the license file for more information.