I think Sure is just want SC provide some filtering query on the server side, we don't need to let the server cached all the query result. We just let the client to find out what they want to know, server don't need to send all the data to the client unless the client wants them.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Nov 9, 2018 at 5:47 AM wjm wjm <zzz...@gmail.com> wrote: > > that will cause SC cache results by different query parameters, is it too > heavy? > > even has 2k instances , but client query by data version, if not changed, > only response 304 NOT MODIFIED > if instances changed, and response size is big, then can response with > compress > so there is no problem? > > Sure <sure_0...@qq.com> 于2018年11月7日周三 下午11:36写道： > > > https://github.com/apache/incubator-servicecomb-service-center/issues/482 > > > > Hi guys, > > > > Our system has 20+ services, and each service has 2k instances at most. > > All the instances are grouped by some labels(in Properties). > > > > We are now querying all the instances from SC, and then filtering them by > > labels on the client side. This wastes a lot of bandwidth and has poor > > performance. Can SC's API provide the filtering function? > > > > Thx.
