# codingapi/tx-lcn

LCN distributed transaction framework, compatible with dubbo, spring cloud and Motan framework, supports various relational databases

Repository: https://github.com/codingapi/tx-lcn
Canonical: https://ross.abutalabs.com/products/tx-lcn
Homepage: https://www.codingapi.com
Language: Java
License: Apache-2.0
License Family: permissive
Topics: tx-lcn, motan, spring-cloud, dubbo, transaction, jta
Last push: 2023-09-06T07:27:14+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": 3217, "days_push": 1092, "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 4164, forks 1437 (observed 2026-08-28T04:08:37.855394+00:00)

## What it is
TX-LCN is a Java distributed transaction framework providing consistent transactions across microservices, compatible with Dubbo, Spring Cloud, and Motan RPC frameworks. It includes a transaction client (TC), transaction manager (TM), and communication protocol modules, supporting relational databases.

## Use cases
- manage distributed transactions across spring cloud microservices
- ensure data consistency with dubbo rpc calls
- coordinate transactions across multiple databases
- add distributed transaction support to motan services
- implement saga or tcc transaction patterns in java
- replace jta with a lightweight distributed transaction coordinator

## When to choose
- you have java microservices using dubbo, spring cloud, or motan needing cross-service transactional consistency
- you want a dedicated transaction coordinator (TM) separate from application clients (TC)
- your stack uses relational databases like mysql

## When to avoid
- you use non-JVM languages or non-relational databases
- you prefer modern alternatives like Seata with a larger active community
- your services can tolerate eventual consistency without distributed transactions

## Facets
- artifact type: framework
- maturity: maintenance
- function: database, middleware, rpc
- domain: microservices, databases, backend
- platform: jvm
- tags: distributed-transactions, lcn, dubbo, spring-cloud, motan, jta, transaction-manager, spring

## Member repositories
- codingapi/tx-lcn (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:37.855394+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-29T18:22:47.321561+00:00, confidence not recorded.
  - readme: https://github.com/codingapi/tx-lcn (fetched 2026-08-28T04:08:37.855394+00:00, sha 7bec2a7c2da7)
- Data as of 2026-08-30T08:39:29.467469+00:00.