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

apache/servicecomb-service-center

A standalone service center to allow services to register their instance information and to discover providers of a given service observed · 2026-08-28

github.com/apache/servicecomb-service-center · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

73/100

  • Activity 82
  • Release rhythm 45
  • Longevity 100
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: 3394
  • days_rel: 152
  • days_push: 110
  • n_releases_24m: 1

Full methodology

Adoption not part of the score

1346 stars · 343 forks observed · 2026-08-28

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

Apache ServiceComb Service-Center is a RESTful service registry that enables microservices to register their instances and discover providers of a given service. It is built on the Open API format and includes a web portal, RBAC security, metrics, tracing, and a CLI for microservice management.

Use cases

  • register and discover microservice instances
  • manage microservice metadata and Open API docs
  • get notified of instance changes via websocket subscription
  • control service discovery access with role-based access control
  • monitor microservices with Prometheus metrics and Zipkin tracing
  • synchronize service registry across multiple clusters
  • manage services through a web portal

When to choose

  • you need a standalone service registry for a microservice architecture
  • you want Open API-based service discovery with fault tolerance and dynamic routing
  • you need built-in metrics, tracing, and a management portal out of the box
  • you use the Apache ServiceComb ecosystem or Java/Go microservices

When to avoid

  • you need a general-purpose key-value store rather than a service registry
  • your stack already standardizes on another registry like Consul, etcd, or Eureka
  • you only need client-side load balancing without centralized discovery

Facets

service · maturity active

service-discovery http-server api-framework websocket monitoring tracing auth cli microservices apis backend developer-tools windows go cross-platform service-registry service-mesh open-api microservice-management apache-servicecomb rbac prometheus-metrics zipkin-tracing web-portal linux macos docker

1 source

Member repositories

RepositoryRoleHealth v2
apache/servicecomb-service-centermain73

For agents

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

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