Ok, thanks for the explanation. Yes, this is a good feature, and I've had this in mind for some time.
Ticket filed: https://issues.apache.org/jira/browse/IGNITE-13037 There are no immediate plans, but I think there is a possibility to achieve this by the end of the year. On Tue, May 19, 2020 at 2:52 PM Marty Jones <[email protected]> wrote: > The use case is having a local cache that stores most widely used cache > items in memory on server instead of having the network expense of pulling > them down every time they are requested. The main thing is the near cache > has to support removing cache items that have expired on the server. > > The best use case I have is a web application that needs a cache item per > request. we would not want to pull the cache item from the cluster every > request. It would be way more efficient for the thin client to have a > near cache that would hold "hot" cache items that are requested frequently. > > On Tue, May 19, 2020 at 3:43 AM Pavel Tupitsyn <[email protected]> > wrote: > >> Can you please describe the use case in more detail? >> What do you expect from such a feature? >> >> On Tue, May 19, 2020 at 2:01 AM [email protected] < >> [email protected]> wrote: >> >>> I wanted to see if there are any plans to support near caches for thin >>> clients? I think it would be a great feature. I know I could use it right >>> now. >>> ------------------------------ >>> Sent from the Apache Ignite Users mailing list archive >>> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. >>> >>
