Ross ROSS = Recommend OSS · open-source software intelligence for agents

QNJR-GROUP/EasyTransaction

A distribute transaction solution(分布式事务) unified the usage of TCC , SAGA ,FMT (seata/fescar AutoCompensation), reliable message, compensate and so on; observed · 2026-08-28

github.com/QNJR-GROUP/EasyTransaction · Java · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

23/100

  • Activity 0
  • Release rhythm 8
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 3445
  • days_rel: n/a
  • days_push: 1057
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

2350 stars · 794 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

framework · maturity maintenance

microservices message-queue middleware database concurrency microservices backend developer-tools jvm self-hosted distributed-transactions tcc saga reliable-message compensation seata-at eventual-consistency spring spring-boot

1 source

Member repositories

RepositoryRoleHealth v2
QNJR-GROUP/EasyTransactionmain23

For agents

markdown · JSON · MCP: product_card(name="QNJR-GROUP/EasyTransaction")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem