Apache ServiceComb Service-Center is a Restful based service-registry that provides micro-services discovery and micro-service management. It is based on Open API format and provides features like service-discovery, fault-tolerance, dynamic routing, notify subscription and scalable by design. It has high performance cache design and separate entity management for micro-services and their instances. It provides out of box support for metrics and tracing. It has a web portal to manage the micro-services.
Open API: API doc(Open API format) management for microservice
Portal: Awesome web portal
Metrics: Able to expose Prometheus metric API automatically
Tracing: Able to report tracing data to Zipkin server
Pluginable: Able to load custom authentication, tls and other dynamic libraries
CLI: Easy to control service center
Kubernetes: Embrace kubernetes ecosystem and support multi cluster service discovery
Datacenters: Additional layer of abstraction to clusters deployed in multiple datacenters
Aggregation: Able to aggregate microservices from multiple registry platforms and support platform registry and client side registry at the same time
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.
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 = "http://127.0.0.1:2380" # manager_cluster = "sc-0=http://127.0.0.1:2380" # 2. if registry_plugin equals to 'etcd' # manager_cluster = "127.0.0.1:2379" manager_cluster = "127.0.0.1:2379"
By default the SC comes up on 127.0.0.1:30100, however you can change the configuration of these address over here.
vi conf/app.conf httpaddr = 127.0.0.1 httpport = 30100
Download the Code
git clone https://github.com/apache/servicecomb-service-center.git $GOPATH/src/github.com/apache/servicecomb-service-center cd $GOPATH/src/github.com/apache/servicecomb-service-center
By default, we use glide(version: 0.13+) to manage dependencies. If the go version greater then
you can download dependencies directly using command
go mod. Please follow below steps to
download all the dependency.
# greater then go1.11 GO111MODULE=on go mod download GO111MODULE=on go mod vendor # lower than go1.11 curl https://glide.sh/get | sh glide install
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).
wget https://github.com/coreos/etcd/releases/download/v3.1.8/etcd-v3.1.8-linux-amd64.tar.gz tar -xvf etcd-v3.1.8-linux-amd64.tar.gz cd etcd-v3.1.8-linux-amd64 ./etcd cd $GOPATH/src/github.com/apache/servicecomb-service-center cp -r ./etc/conf . ./service-center
This will bring up Service Center listening on ip/port 127.0.0.1:30100 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).
You can download our latest release from ServiceComb Website and then untar it and run start-frontend.sh/start-frontend.bat. This will bring up the Service-Center UI on http://127.0.0.1:30103.
Note: By default frontend runs on 127.0.0.1, if you want to change this then you can change it in
You can follow the guide over here to run the Frontend from source.
See Contribution guide for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.