beiwei30 commented on a change in pull request #62: URL: https://github.com/apache/dubbo-go-samples/pull/62#discussion_r590368448
########## File path: configcenter/README.md ########## @@ -0,0 +1,95 @@ +# Config Center Sample + +### Background + +In Dubbo, config center takes the following two responsibilities: +1. For externalized configuration. Central management for bootstrap configurations, that is, keep "dubbo.properties" save externally on the config center. +2. For service governance. Keep service rule on the config center, and notify the subscribers when the rule changes. + +The purpose of externalized configuration is centrally managing application's configurations in one single place. There are many mature configuration management systems in the industry. Dubbo go supports some of them, including Zookeeper, Nacos and Apollo, etc. + +There's no difference between externalized configuration and local configuration with regarding the content and the format. Config center is more suitable to keep the common configurations such as registry center configuration, metadata center configuration, etc., so that they are centrally managed. + +At the same time, externalized configuration has two scope: global scope, and application scope. Global scope configurations are shared among all applications, and application scope configuration is only visible to the application it belongs to. By default, externalized configuration has higher priority than the local configuration. + +This sample demonstrates how to config and use externalized configuration on Zookeeper. You can refer [Dubbo Documentation](https://dubbo.apache.org/zh/docs/v2.7/user/configuration/config-center/) for more details on config center. + +### Example + +If use Zookeeper as config center, global externalized configuration and application scope configurations will be layout like below: + +``` +dubbo +└── config + ├── dubbo + │ └── dubbo.properties <- 全局 Review comment: done. ########## File path: configcenter/README.md ########## @@ -0,0 +1,95 @@ +# Config Center Sample + +### Background + +In Dubbo, config center takes the following two responsibilities: +1. For externalized configuration. Central management for bootstrap configurations, that is, keep "dubbo.properties" save externally on the config center. +2. For service governance. Keep service rule on the config center, and notify the subscribers when the rule changes. + +The purpose of externalized configuration is centrally managing application's configurations in one single place. There are many mature configuration management systems in the industry. Dubbo go supports some of them, including Zookeeper, Nacos and Apollo, etc. + +There's no difference between externalized configuration and local configuration with regarding the content and the format. Config center is more suitable to keep the common configurations such as registry center configuration, metadata center configuration, etc., so that they are centrally managed. + +At the same time, externalized configuration has two scope: global scope, and application scope. Global scope configurations are shared among all applications, and application scope configuration is only visible to the application it belongs to. By default, externalized configuration has higher priority than the local configuration. + +This sample demonstrates how to config and use externalized configuration on Zookeeper. You can refer [Dubbo Documentation](https://dubbo.apache.org/zh/docs/v2.7/user/configuration/config-center/) for more details on config center. + +### Example + +If use Zookeeper as config center, global externalized configuration and application scope configurations will be layout like below: + +``` +dubbo +└── config + ├── dubbo + │ └── dubbo.properties <- 全局 + ├── user-info-client + │ └── dubbo.properties <- 服务消费者 Review comment: done. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
