中文文档

A lightweight distributed transaction manager

DTM is the first golang open source distributed transaction project. It elegantly resolve the problem of execution out of order. In the microservice architecture, a high-performance and easy-to-use distributed transaction solution is provided.

Who's using dtm

Ivydad 常青藤爸爸

Eglass 视咖镜小二

Characteristic

Stable and reliable
- Tested in the production environment, unit test coverage is over 90%
Simple to use
- The interface is simple, developers no longer worry about suspension, null compensation, idempotence, etc., and the framework layer takes care of them.
Multi language supported
- It is suitable for companies with multi-language stacks. The protocol supports http. Convenient to use in various languages such as go, python, php, nodejs, ruby.
Easy to deploy, easy to expand
- Only rely on mysql, easy to deploy, easy to expand horizontally
Multiple distributed transaction protocol supported
- TCC: Try-Confirm-Cancel
- SAGA:
- Reliable news
- XA

dtm vs other

At present, the open source distributed transaction framework has not yet seen a mature framework for non-Java languages. There are many Java projects, such as Ali's SEATA, Huawei's ServiceComb-Pack, JD's shardingsphere, and himly, tcc-transaction, ByteTCC, etc. Among them, seata is the most widely used.

The following is a comparison of the main features of dtm and seata:

Features	DTM	SEATA	Remarks
Supported languages	Golang, python, php and others	Java	dtm can easily support a new language
Exception Handling	Sub-transaction barrier automatic processing	Manual processing	dtm solves idempotence, suspension, and null compensation
TCC	✓	✓
XA	✓	✓
AT	✗	✓	AT is similar to XA, with better performance but dirty rollback
SAGA	simple mode	state machine complex mode	dtm's state machine mode is under planning
Transaction message	✓	✗	dtm provides transaction messages similar to rocketmq
Communication protocol	HTTP	dubbo and other protocols, no HTTP	dtm will support grpc protocol in the future
star number			dtm releases 0.1 from 20210604, fast development

From the features of the comparison above, if your language stack includes languages other than Java, then dtm is your first choice. If your language stack is Java, you can also choose to access dtm and use sub-transaction barrier technology to simplify your business writing.

Quick start

Installation

git clone https://github.com/yedf/dtm

DTM depends on mysql

Configure mysql:

cp conf.sample.yml conf.yml # Modify conf.yml

Start and run the saga example

go run app/main.go

Start using

Use

  // business microservice address
  const qsBusi = "http://localhost:8081/api/busi_saga"
  req := &gin.H{"amount": 30} // Microservice payload
  // The address where DtmServer serves DTM, which is a url
  DtmServer := "http://localhost:8080/api/dtmsvr"
  saga := dtmcli.NewSaga(DtmServer, dtmcli.MustGenGid(DtmServer)).
    // Add a TransOut sub-transaction, the operation is url: qsBusi+"/TransOut"，
    // compensation operation is url: qsBusi+"/TransOutCompensate"
    Add(qsBusi+"/TransOut", qsBusi+"/TransOutCompensate", req).
    // Add a TransIn sub-transaction, the operation is url: qsBusi+"/TransOut"，
    // compensation operation is url: qsBusi+"/TransInCompensate"
    Add(qsBusi+"/TransIn", qsBusi+"/TransInCompensate", req)
  // Submit the saga transaction, dtm will complete all sub-transactions/rollback all sub-transactions
  err := saga.Submit()