Are you going to provide a client API for watching instance change? Which will hide all implementation details of event pushing(whether websocket or messaging queue). Otherwise it will be quite complicated for client side code to implement all service center discovery features.
I am not taking PUSH as a better way than PULL. In many scenarios, PULL will give much more reliability. Although PUSH will give some real time improvement, but we do not find any big problems in PULL yet now. ------------------ ???????? ------------------ ??????: "Xiaoliang Tian"<[email protected]>; ????????: 2018??11??7??(??????) ????10:34 ??????: "dev"<[email protected]>; ????: Re: [DISCUSS]SC Push Instance Event Through Kafka +1 for this event pushing, Service center has so many work to do which caused more load average, user may not even need it. making event pushing as a optional feature just like java chassis did will improve perf of service center. besides, by using mature community solution will increase the stability and availability of service center event pushing feature. Sure <[email protected]> ??2018??11??7?????? ????10:23?????? > Now, the way sc push instance event to Microservices is based on > websocket. This will lose events when connection is broken. > > > So, I think we can add a new optional way that push events into the MQ > like kafka, and Microservices can subscribe it and no longer lose the > messages from sc. > > > It has another benefit is that sc no need to repeat the same feature keep > alive millions connections like MQ component.
