Added incubating to the release kit name
7 files changed
tree: 9c4beadad703ecb1da074dab1954e5ad33c2bfe8
  1. .github/
  2. .gitignore
  3. .gitmodules
  4. .travis.yml
  9. docs/
  10. etc/
  11. examples/
  12. frontend/
  13. integration/
  14. licenses/
  15. main.go
  16. pkg/
  17. scripts/
  18. server/
  19. vendor/
  20. version/


Build Status Coverage Status Go Report Card GoDoc HitCount

Apache ServiceComb (incubating) service-center allows services to register their instance information and to discover providers of a given service.


  • Open API: API doc(Open API format) management for microservice
  • Metadata: Metadata management for both microservice and microservice instance
  • Dependency: Microservice dependency management
  • Seperated: Seperated microservice and microservice instance entity management
  • Domains: Logical multiple domains management
  • Security: White and back list configuration for service discovery
  • Discovery: Support query instance by criteria
  • Subscribe: Use web socket to notify client about instance change events
  • Portal: Awesome web portal
  • Fault tolerance: Multiple fault tolerance mechanism and design in the architecture
  • Performance: Performance/Caching design
  • Metrics: Able to expose Prometheus metric API automatically
  • Tracing: Able to report tracing data to Zipkin server


Project documentation is available on the ServiceComb website. You can also find some development guide here.

Quick Start

Getting Service Center

The easiest way to get Service Center is to use one of the pre-built release binaries which are available for Linux, Windows and Docker.

Running Service Center using the Release

You can download our latest release from ServiceComb Website.When you get these release, you can execute the start script to run Service Center.






docker pull servicecomb/service-center
docker run -d -p 30100:30100 servicecomb/service-center

Note: The Releases of Service-Center uses emebeded etcd, if you want to use the seperate instance of etcd then you can deploy the etcd seperately and configure the etcd ip over here.

vi conf/app.conf

## Edit this file
# registry address
# 1. if registry_plugin equals to 'embeded_etcd'
# manager_name = "sc-0"
# manager_addr = ""
# manager_cluster = "sc-0="
# 2. if registry_plugin equals to 'etcd'
# manager_cluster = ""
manager_cluster = ""

By default the SC comes up on, however you can change the configuration of these address over here.

vi conf/app.conf

httpaddr =
httpport = 30100

Building & Running Service-Center from source

Download the Code

git clone $GOPATH/src/
cd $GOPATH/src/


We use gvt for dependency management, please follow below steps to download all the dependency.

go get
gvt restore

If you face any issue in downloading the dependency because of insecure connection then you can use gvt restore -precaire

Build the Service-Center

go build -o service-center

First, you need to run a etcd(version: 3.x) as a database service and then modify the etcd IP and port in the Service Center configuration file (./etc/conf/app.conf : manager_cluster).

tar -xvf etcd-v3.1.8-linux-amd64.tar.gz
cd etcd-v3.1.8-linux-amd64

cd $GOPATH/src/
cp -r ./etc/conf .

This will bring up Service Center listening on ip/port for service communication.If you want to change the listening ip/port, you can modify it in the Service Center configuration file (./conf/app.conf : httpaddr,httpport).

Running Frontend using the Release

You can download our latest release from ServiceComb Website and then untar it and run This will bring up the Service-Center UI on





Note: By default frontend runs on, if you want to change this then you can change it in conf/app.conf.


You can also change the the IP of Service-Center to which Frontend is connected over here app/apiList/apiList.js

You can follow the guide over here to run the Frontend from source.


Bugs: issues


See Contribution guide for details on submitting patches and the contribution workflow.

Reporting Issues

See reporting bugs for details about reporting any issues.