I agree with kevin Clair. I don??t think it is necessary to provide so many ways to synchronize using the configuration center. Maybe we can separate the synchronization of the gateway and admin from the management page, similar to the nameserver of rocketMQ
------------------ ???????? ------------------ ??????: "dev" <xia...@apache.org>; ????????: 2021??5??25??(??????) ????5:00 ??????: "dev"<dev@shenyu.apache.org>; ????: Re: Discuss ShenYu support other config center Hi kevin Clair I couldn't agree with you more For now, it's too hard for developers, so should we provide a lot of defaults for users to choose from, and subsequently we can use SPI to abstract and let users to extend themselves Kevin Clair <kevincl...@apache.org> ??2021??5??25?????? ????4:54?????? > Maybe we can open an entry for users to develop their own data > synchronization, if Shenyu's current data synchronization mode is not > satisfied. Similar to our custom development plug. > > XiaoYu <xia...@apache.org> ??2021??5??25?????? ????4:18?????? > > > Hi Community > > > > For ShenYu , data configuration and synchronization is a very important > > feature. > > > > Currently we have 4 kinds of synchronization methods, http, websocket, > > nacos, zookeeper, do we need to add other synchronization methods, such > as > > apollo [1], etcd [2], consul [3]. > > > > Welcome to discuss in the comments and look forward to better > suggestions. > > > > [1] https://github.com/ctripcorp/apollo > > [2] https://github.com/etcd-io/etcd > > [3] https://github.com/hashicorp/consul > > > > Translated with www.DeepL.com/Translator (free version) > > >