dongzl commented on issue #3162: ShardingSphere Config Center implemention for Apollo. URL: https://github.com/apache/incubator-shardingsphere/issues/3162#issuecomment-539365908 Hi @terrymanu, I have communicated with Apollo team, they think read config and modify config design for different roles, so they split the Apollo API. For read config API design for application system, it is high availability, and it is not any limit. But for modify config API design for other config system to sync configuration to Apollo, it need token validation and must have modify config rights, they think modify config must be very careful, if operate error, it make a mistake for application system. So they split the Apollo API. `apollo-client` is for application system，it provide read config API and monitor config change API; `apollo-openapi` is for other config system, it provide read config API and modify config API. This is the discuss issue: https://github.com/ctripcorp/apollo/issues/2635 In ShardingSphere `org.apache.shardingsphere.orchestration.config.api.ConfigCenter` interface have read and modify API. I think we still have to integrate the two client API. Do you have other suggestions?
---------------------------------------------------------------- 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] With regards, Apache Git Services
