# QNJR-GROUP/EasyTransaction

A distribute transaction solution（分布式事务） unified the usage of TCC , SAGA ,FMT (seata/fescar AutoCompensation)， reliable message, compensate and so on;

Repository: https://github.com/QNJR-GROUP/EasyTransaction
Canonical: https://ross.abutalabs.com/products/easytransaction
Language: Java
License: Apache-2.0
License Family: permissive
Topics: transaction, tcc, base, saga, distributed-transaction
Last push: 2023-10-11T21:05:57+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3445, "days_push": 1057, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2350, forks 794 (observed 2026-08-28T04:06:40.336531+00:00)

## What it is
EasyTransaction is a Java/Spring framework providing a unified solution for distributed transactions across microservices and SOA systems. It bundles multiple transaction patterns—TCC, SAGA, traditional compensation, Seata/Fescar-style auto-compensation (AT), and reliable messaging—behind one consistent API with built-in idempotency and crash recovery.

## Use cases
- implement TCC transactions across microservices
- achieve eventual consistency with reliable message queues
- use SAGA or compensation patterns for distributed workflows
- integrate Seata AT auto-compensation transactions
- handle crash recovery and idempotency in distributed transactions
- avoid deploying a separate transaction coordinator or ZooKeeper

## When to choose
- your Spring Boot services need multiple distributed transaction styles under one framework
- you want TCC, SAGA, compensation, and reliable messaging without deploying an external coordinator
- you need built-in idempotency, call-order handling, and crash recovery
- you want low-overhead transactions with minimal database footprint

## When to avoid
- your system fits in a single database transaction and needs no distributed coordination
- you use a non-Java or non-Spring stack
- you need a very actively developed project with frequent releases
- you require hot-record-heavy auto-compensation workloads where performance degrades

## Facets
- artifact type: framework
- maturity: maintenance
- function: microservices, message-queue, middleware, database, concurrency
- domain: microservices, backend, developer-tools
- platform: jvm, self-hosted
- tags: distributed-transactions, tcc, saga, reliable-message, compensation, seata-at, eventual-consistency, spring, spring-boot

## Member repositories
- QNJR-GROUP/EasyTransaction (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:40.336531+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:36:55.474936+00:00, confidence not recorded.
  - readme: https://github.com/QNJR-GROUP/EasyTransaction (fetched 2026-08-28T04:06:40.336531+00:00, sha 6a26fdb00884)
- Data as of 2026-08-30T08:39:29.467469+00:00.