Update log
- Add environment variable support, deployment support, document add deployment support
- dtmcli is completely decoupled from gin and logrus, and supports splitting into separate warehouses
- Add transaction wait result mode
- Add the default DB_DRIVER to mysql
DTM is the first golang open source distributed transaction manager, which elegantly solves distributed transaction problems such as idempotence, null compensation, and suspension. Provides a simple, easy-to-use, high-performance, and easily horizontally scalable distributed transaction solution.
Invited to participate in the China Database Conference to share distributed transaction practice in a multilingual environment
Who is using dtm
Eglass Sight Coffee Mirror Small Two
Highlights
Extremely easy to access
- Support HTTP, provide a very simple interface, greatly reduce the difficulty of getting started with distributed transactions, and novices can quickly access
Simple to use
- Developers no longer worry about suspension, null compensation, idempotence, etc., and the framework will handle it on their behalf
Cross language
- It is suitable for companies with multi-language stacks. Convenient to use in various languages such as go, python, php, nodejs, ruby, and c#.
Easy to deploy, easy to expand
- Only rely on mysql, easy to deploy, easy to cluster, easy to expand horizontally
Multiple distributed transaction protocol support
- TCC, SAGA, XA, transaction news
Compared with other frameworks
At present, the open source distributed transaction framework has not yet seen a mature framework for non-Java languages. There are many Java languages, such as Ali's SEATA, Huawei's ServiceComb-Pack, JD's shardingsphere, and himly, tcc-transaction, ByteTCC, etc., among which seata is the most widely used.
The following is a comparison of the main features of dtm and seata:
characteristic | DTM | SEATA | Remark |
---|---|---|---|
Support language | Go、Java、python、php、c#... | Java | dtm can easily access a new language |
Exception handling | Sub-transaction barrier automatic processing | Manual processing | dtm solves idempotence, suspension, and null compensation |
TCC affairs | ✓ | ✓ | |
XA affairs | ✓ | ✓ | |
AT affairs | ✗ | ✓ | AT is similar to XA, with better performance, but with dirty rollback |
SAGA affairs | Simple mode | State machine complex pattern | The state machine mode of dtm is under planning |
Transaction message | ✓ | ✗ | dtm provides transaction messages similar to rocketmq |
letter of agreement | HTTP、GRPC | Protocols such as dubbo, no HTTP | dtm is more cloud-native |
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.
If you think https://github.com/yedf/dtm good or helpful to you, please give me a star!
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用
。你还可以使用@
来通知其他用户。