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

apache/incubator-seata

:fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution. observed · 2026-08-28

github.com/apache/incubator-seata · homepage · Java · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

80/100

  • Activity 99
  • Release rhythm 44
  • Longevity 100
How is this computed?

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

  • gap_med: 131.0
  • age_days: 2805
  • days_rel: 217
  • days_push: 9
  • n_releases_24m: 5

Full methodology

Adoption not part of the score

25992 stars · 8853 forks observed · 2026-08-28

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

Apache Seata (incubating) is an open-source, high-performance distributed transaction solution for microservices architectures. It provides AT, TCC, SAGA, and XA transaction modes to maintain data consistency across services with separate databases.

Use cases

  • ensure data consistency across microservices with separate databases
  • manage distributed transactions spanning multiple services
  • implement saga-based long-running transactions
  • add non-intrusive automatic rollback for JDBC-based services
  • coordinate TCC transactions in a Java microservices stack
  • maintain consistency during cross-service order and payment flows

When to choose

  • you run Java microservices with a database-per-service pattern and need cross-service ACID guarantees
  • you want a non-intrusive AT mode that works with JDBC and relational databases like MySQL, PostgreSQL, or Oracle
  • you need multiple transaction models (AT, TCC, SAGA, XA) in one solution
  • you use RPC frameworks like Dubbo, Spring Cloud, gRPC, or Sofa-RPC

When to avoid

  • your application is a monolith with a single local database where local transactions suffice
  • you need distributed transactions in non-JVM languages, as Seata is Java-centric
  • you prefer eventual consistency via messaging/event sourcing rather than coordinated transactions
  • you cannot operate the additional Seata transaction coordinator (TC) server component

Facets

library · maturity stable

microservices middleware database rpc concurrency microservices databases backend fintech jvm cross-platform distributed-transactions saga tcc xa at-mode data-consistency two-phase-commit spring-cloud dubbo docker kubernetes

10 sources

Member repositories

RepositoryRoleHealth v2
apache/incubator-seatamain80

For agents

markdown · JSON · MCP: product_card(name="apache/incubator-seata")

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