Hi Folks,

What do you think about the idea of supporting a lightweight cache over
records in the thin client?

In the thick client we have near caches (yes, of course, they add
complexity to the product). There is no such option in the thin one.

Yes, you can cache this with third-party tools like guava. At the same
time, my idea is that the product could somehow notify such mini-cache
about changes (probably in batches).

For some scenarios, asking server nodes for the rarely changed cache value
is overhead. And I remember Ignite 1.x caches were on-heap (without
off-heap - on-heap data copying cost)

Sincerely,
Dmitriy Pavlov

Reply via email to