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

apache/servicecomb-pack

Apache ServiceComb Pack is an eventually data consistency solution for micro-service applications. ServiceComb Pack currently provides TCC and Saga distributed transaction co-ordination solutions by using Alpha as a transaction coordinator and Omega as an transaction agent . observed · 2026-08-28

github.com/apache/servicecomb-pack · homepage · Java · Apache-2.0 (permissive) · archived observed · 2026-08-28

Health v2 · maintenance only

10/100

  • Activity 0
  • Release rhythm 8
  • Longevity 100

Flags: archived

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: 3333
  • days_rel: n/a
  • days_push: 699
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1912 stars · 427 forks observed · 2026-08-28

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

Apache ServiceComb Pack is an eventually consistent distributed transaction solution for microservice applications, providing Saga and TCC coordination protocols. It consists of Alpha, a stateless transaction coordinator that persists transaction events to a database, and Omega, an in-process agent that intercepts requests and reports events over gRPC.

Use cases

  • coordinate distributed transactions across microservices
  • implement saga pattern with compensating transactions
  • add TCC (try-confirm-cancel) transactions to Java microservices
  • ensure eventual data consistency when a service call fails mid-workflow
  • run a highly available transaction coordinator with persistent event storage
  • add transaction boundaries with minimal annotations in Spring Boot services

When to choose

  • you need saga or TCC distributed transactions in a JVM/Spring-based microservice system
  • you want low-invasion transaction coordination via annotations and compensation methods
  • you need durable, database-backed transaction event storage with a stateless coordinator for HA

When to avoid

  • you need an actively maintained project - the maintainers state it is inactive due to lack of maintainers
  • your stack is not JVM-based (only community Go/C# Omega ports exist, unofficial)
  • you only need simple local transactions or a modern alternative like Seata or Temporal

Facets

framework · maturity abandoned

microservices middleware rpc serialization database microservices backend developer-tools jvm cross-platform distributed-transactions saga tcc eventual-consistency transaction-coordination grpc compensation docker

8 sources

Member repositories

RepositoryRoleHealth v2
apache/servicecomb-packmain10

For agents

markdown · JSON · MCP: product_card(name="apache/servicecomb-pack")

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