# apache/servicecomb-service-center

A standalone service center to allow services to register their instance information and to discover providers of a given service

Repository: https://github.com/apache/servicecomb-service-center
Canonical: https://ross.abutalabs.com/products/servicecomb-service-center
Language: Go
License: Apache-2.0
License Family: permissive
Topics: servicecomb
Last push: 2026-05-15T22:52:45+00:00

## Health v2 (maintenance only)
Score: 73/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 82, release rhythm 45, longevity 100
- inputs: {"age_days": 3394, "days_push": 110, "days_rel": 152, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1346, forks 343 (observed 2026-08-28T04:04:27.512325+00:00)

## What it is
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
- artifact type: service
- maturity: active
- function: service-discovery, http-server, api-framework, websocket, monitoring, tracing, auth, cli
- domain: microservices, apis, backend, developer-tools
- platform: windows, go, cross-platform
- tags: service-registry, service-mesh, open-api, microservice-management, apache-servicecomb, rbac, prometheus-metrics, zipkin-tracing, web-portal, linux, macos, docker

## Member repositories
- apache/servicecomb-service-center (main) score 73

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:27.512325+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-30T04:42:40.879103+00:00, confidence not recorded.
  - readme: https://github.com/apache/servicecomb-service-center (fetched 2026-08-28T04:04:27.512325+00:00, sha 78edc651b1f0)
- Data as of 2026-08-30T08:39:29.467469+00:00.