Hi Pavel, Thank you for details. Is there a way to improve performance in such subsequent requests ?
Scenario is - lets say cache is storing data e.g. 1 million list of custom poco class objects. Now it needs only one specific poco object out of it. Here this operation would fetch full cache i.e. 1 million rows then filter that specific object. I read about cache querying here - https://apacheignite.readme.io/docs/cache-queries Now question is does this cache query asks 1) for full data first & then filter or 2) it is optimized enough to query server to get only 1 object and not like 1) On Friday, November 8, 2019, Pavel Tupitsyn <ptupit...@apache.org> wrote: > Hi, > > Every request is communicated to the server, there is no "local cache" or > anything like that. > > On Fri, Nov 8, 2019 at 8:37 PM Sudhir Patil <patilsudhi...@gmail.com> > wrote: > >> Hi All, >> >> In ignite.net server node stores cache data and a thin client >> communicates with server to get cache data. >> >> In such situations, post 1 request of cache data by thin client, does all >> further requests still communicate with server or it stores that cache data >> on thin client and server from there and do not communicate with server ?? >> >> Regards, >> Sudhir >> >> >> -- >> Thanks & Regards, >> Sudhir Patil, >> +91 9881095647. >> > -- Thanks & Regards, Sudhir Patil, +91 9881095647.
