Now, service center has supported multiple datacenters deployment. Its architecture likes below.
As shown in the figure, we deploy an SC(Service-Center) cluster independently under each DC(datacenter). Each SC cluster manages the micro-service instances under the DC under which it belongs, and the DCs are isolated from each other. Another implementation of the discovery plug-in,
Service-Center Aggregate service, can access multiple SC instances and periodically pull up micro-service instance information so that if some micro-services can request aggregate, cross-DCs can be implemented using the same API as SC cluster.
If SC aggregate is not deployed globally, SC also supports another way to implement multiple DCs discovery, as shown below.
The difference between the two approaches is that global deployment aggregate can divert service discovery traffic, the whole architecture is more like a read-write separation architecture, and the SC of each DC manage microservice information independently, which reduces the complexity. So we recommend the first architecture.
Let's assume you want to install 2 clusters of Service-Center in different DCs with following details.
you can follow this guide to install Service-Center in cluster mode. After that, we can deploy a Service-Center Aggregate service now.
Edit the configuration of the ip/port on which SC aggregate will run, we assume you launch it at 10.12.0.3.
vi conf/app.conf # Replace the below values httpaddr = 10.12.0.3 discovery_plugin = servicecenter registry_plugin = buildin self_register = 0 manager_cluster = "sc-1=http://10.12.0.1:30100,sc-2=http://10.12.0.2:30100" # Start the Service-center ./service-center
Note: Please don't run start.sh as it will also start the etcd.
scctl --addr http://10.12.0.3:30100 get cluster # CLUSTER | ENDPOINTS # +---------+-------------------------+ # sc-1 | http://10.12.0.1:30100 # sc-2 | http://10.12.0.2:30100
go-chassis application can run perfectly in the above 2 architectures. If you are using
java-chassis, there are only support the service center with the second architecture at the moment. You can ref to
here for more details of the second architecture.
Edit the configuration of the ip/port on which Server will register.
Replace the below values
cse: service: registry: type: servicecenter address: http://10.12.0.2:30100 # the address of SC in dc-2
Run the Server
go run examples/discovery/server/main.go
Edit the configuration of the ip/port on which Client will register and discover.
Replace the below values
cse: service: registry: registrator: type: servicecenter address: http://10.12.0.1:30100 # the address of SC in dc-1 serviceDiscovery: type: servicecenter address: http://10.12.0.3:30100 # the address of SC Aggregate
Run the Client
go run examples/discovery/client/main.go
Since client is not a service, we check its running log.
2018-09-29 10:30:25.556 +08:00 INFO registry/bootstrap.go:69 Register [Client] success ... 2018-09-29 10:30:25.566 +08:00 WARN servicecenter/servicecenter.go:324 55c783c5c38e11e8951f0a58ac00011d Get instances from remote, key: default Server 2018-09-29 10:30:25.566 +08:00 INFO client/client_manager.go:86 Create client for highway:Server:127.0.0.1:8082 ... 2018/09/29 10:30:25 AddEmploy ------------------------------ employList:<name:"One" phone:"15989351111" >