[
https://issues.apache.org/jira/browse/SCB-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684831#comment-16684831
]
ASF GitHub Bot commented on SCB-993:
------------------------------------
asifdxtreme closed pull request #486: SCB-993 Update the design document
URL: https://github.com/apache/servicecomb-service-center/pull/486
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/aggregator-design.PNG b/docs/aggregator-design.PNG
index 5f67d1ab..06b4bf72 100644
Binary files a/docs/aggregator-design.PNG and b/docs/aggregator-design.PNG
differ
diff --git a/docs/design.md b/docs/design.md
index 12c73f69..9268fa76 100644
--- a/docs/design.md
+++ b/docs/design.md
@@ -1,10 +1,18 @@
## Service-Center Design
Service-Center(SC) is a service registry that allows services to register
their instance information and to discover providers of a given service.
-SC uses etcd to store all the information of micro-service and its instances.
Below is the diagram stating the working principles and flow of SC.
+Generally, SC uses etcd to store all the information of micro-service and its
instances.
+
+
+
+Below is the diagram stating the working principles and flow of SC.
#### On StartUp
-Here we assume that micro-services are written using
[java-chassis](https://github.com/ServiceComb/java-chassis) sdk. So when
micro-service boots up then java-chassis sdk does the following list of tasks.
+Here describes a standard client registration process.
+We assume that micro-services are written using
+[java-chassis](https://github.com/ServiceComb/java-chassis) sdk or
+[go-chassis](https://github.com/go-chassis/go-chassis) sdk.
+So when micro-service boots up then java-chassis sdk does the following list
of tasks.
1. On startup provider registers the micro-service to SC if not registered
earlier and also register its instance information like its Ip and Port on
which instance is running.
2. SC stores the provider information in etcd.
@@ -23,4 +31,4 @@ Provider instance regularly sends heartbeat signal every 30
seconds to SC, if SC
Consumer watches the information of provider instances from SC and if there is
any change then the cache is updated.
When Consumer needs to communicate to Provider then consumer reads endpoints
of the provider instances from cache and do loadbalancing to communicate to
Provider.
-Note: This document is in beta stage, feel free to contribute to this document.
+Note: Feel free to contribute to this document.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Bug fixes
> ---------
>
> Key: SCB-993
> URL: https://issues.apache.org/jira/browse/SCB-993
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Service-Center
> Reporter: little-cui
> Assignee: little-cui
> Priority: Major
> Fix For: service-center-1.1.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
