# liuyangming/ByteTCC

ByteTCC is a distributed transaction manager based on the TCC(Try/Confirm/Cancel) mechanism. It’s compatible with the JTA specification. User guide: https://github.com/liuyangming/ByteTCC/wiki

Repository: https://github.com/liuyangming/ByteTCC
Canonical: https://ross.abutalabs.com/products/bytetcc
Homepage: https://www.bytesoft.org/
Language: Java
License: LGPL-3.0
License Family: copyleft
Topics: tcc, spring-cloud, dubbo, distributed-transaction, jta, transaction
Last push: 2022-04-15T13:50:00+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3855, "days_push": 1601, "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 2869, forks 901 (observed 2026-08-28T04:07:27.006059+00:00)

## What it is
ByteTCC is a distributed transaction manager for Java based on the Try-Confirm-Cancel (TCC) compensating transaction mechanism, compatible with the JTA specification. It integrates declaratively with Spring, Spring Cloud, and Dubbo to coordinate transactions across multiple datasources, applications, and servers.

## Use cases
- manage distributed transactions across microservices in Java
- implement TCC try-confirm-cancel transactions with Spring
- coordinate transactions across Dubbo RPC services
- handle cross-application multi-datasource transactions
- ensure idempotent service calls in distributed transactions
- run long-lived compensating transactions in Spring Cloud

## When to choose
- you need JTA-compatible distributed transactions in a Spring or Dubbo Java stack
- your microservices require TCC-style compensating transactions with declarative annotations
- you need framework-level idempotence support for transactional services

## When to avoid
- you use non-JVM languages or non-Spring/Dubbo frameworks
- you want an actively developed project - the latest release dates to 2022
- you prefer saga orchestration or modern alternatives like Seata

## Facets
- artifact type: library
- maturity: maintenance
- function: database, middleware, microservices, workflow-automation
- domain: databases, microservices, backend, developer-tools
- platform: jvm, self-hosted
- tags: tcc, distributed-transaction, jta, spring-cloud, dubbo, transaction-manager, saga-pattern, compensating-transactions, spring

## Member repositories
- liuyangming/ByteTCC (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:27.006059+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-30T07:35:55.239355+00:00, confidence not recorded.
  - readme: https://github.com/liuyangming/ByteTCC (fetched 2026-08-28T04:07:27.006059+00:00, sha c2fa5d61b374)
- Data as of 2026-08-30T08:39:29.467469+00:00.