changmingxie/tcc-transaction

Health v2 · maintenance only

Adoption not part of the score

5759 stars · 2749 forks observed · 2026-08-28

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

tcc-transaction is a Java framework implementing TCC (Try-Confirm-Cancel) distributed transactions for microservice architectures. It coordinates multi-service, multi-database operations to achieve eventual consistency through resource reservation, confirmation, and cancellation phases with retry support.

Use cases

• ensure consistency when a payment refund spans multiple merchant accounts in different databases
• coordinate multi-service transactions in a microservices architecture
• implement try-confirm-cancel compensation logic across services
• roll back partial failures when one service call fails mid-workflow
• add distributed transaction support to a Java Spring microservices project

When to choose

• you need strong eventual consistency across multiple services and databases in a JVM microservices stack
• your business logic can naturally be split into resource reservation (Try), commit (Confirm), and rollback (Cancel) steps
• you are building payment, refund, or ledger-style flows requiring atomic multi-account operations

When to avoid

• your services share a single database where local ACID transactions suffice
• you cannot make Confirm/Cancel operations idempotent
• you are not on the JVM or unwilling to add TCC boilerplate to business code
• you prefer simpler saga or message-driven eventual consistency patterns

Facets

framework · maturity stable

microservices middleware database workflow-automation microservices backend databases fintech jvm cross-platform tcc distributed-transactions saga-alternative eventual-consistency spring-integration payment-systems

Member repositories

For agents

markdown · JSON · MCP: product_card(name="changmingxie/tcc-transaction")