You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
当前SC的订阅推送规则的维度为appid/serviceName/version,也就是微服务的维度。但是在实际使用场景下,有诉求按照实例属性(标签)粒度进行订阅。比如说,consumer只关心某个节点上的服务实例的变更,其他节点上的不关心。该节点上是不同微服务下的实例。使用当前的订阅机制的话,consumer就需要将该节点上所有的微服务进行订阅。这样造成的结果是会有很多冗余的推送,对整个系统的性能造成很大的影响。如果可以按照标签订阅的话,每个实例注册的时候可以在property中新增一个nodeId的字段来标识节点信息。consumer订阅时仅将他所关心的对应的nodeID作为规则发给注册中心,后续注册中心根据规则进行推送,可以降低整个系统冗余的推送量。
Describe the solution you'd like
同上
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
当前SC的订阅推送规则的维度为appid/serviceName/version,也就是微服务的维度。但是在实际使用场景下,有诉求按照实例属性(标签)粒度进行订阅。比如说,consumer只关心某个节点上的服务实例的变更,其他节点上的不关心。该节点上是不同微服务下的实例。使用当前的订阅机制的话,consumer就需要将该节点上所有的微服务进行订阅。这样造成的结果是会有很多冗余的推送,对整个系统的性能造成很大的影响。如果可以按照标签订阅的话,每个实例注册的时候可以在property中新增一个nodeId的字段来标识节点信息。consumer订阅时仅将他所关心的对应的nodeID作为规则发给注册中心,后续注册中心根据规则进行推送,可以降低整个系统冗余的推送量。
Describe the solution you'd like
同上
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: