Do you have any evaluation document by using etcd as config center? Now config-cc supports using Huawei Config Center as the backend. And this implementation is based on ectd with an extra abstraction like service center. I am not quite sure if using etcd itself can fitful for users use cases and if it is a good solution or just a workable solution.
Maybe we can make Huawei Config Center opensource and distribute it like service center which is quite simple too. ------------------ ???????? ------------------ ??????: "Yang Bo"<oaky...@gmail.com>; ????????: 2018??11??26??(??????) ????7:30 ??????: "dev"<dev@servicecomb.apache.org>; ????: [Discuss]Adding Etcd as a config center for Java-Chassis Hi, The ServiceComb project does not have a usable config-center and many users have shown concerns about it. (Apollo is too complex to setup and have high learning cure in using/maintaining). I tried to build a config-center around Etcd for Java-Chassis, it's quite simple. Most of the features from the CC(CSE) can be achieved. From my point of view, using Etcd is good for small projects, show cases and in development, because we already have an Etcd instance running(service-center needs it). The code is here(it's just a demonstration, needs improvement): https://github.com/yangbor/servicecomb-java-chassis/tree/cc-etcd Any thoughts? -- Best Regards, Yang.
