Yes, near cache. On Mon, Nov 18, 2024 at 3:01 PM Jeremy McMillan <j...@gridgain.com> wrote:
> When you say "local" cache, do you actually mean "near cache"? > https://ignite.apache.org/docs/latest/configuring-caches/near-cache > > If this is the case, I'd be interested to understand what would be lost > if, hypothetically, you switched to using thin clients and operation > without "near cache." > > If not, I suspect your architecture will likely dictate needing upgrade > downtime for maintenance involving the whole cluster (like version > upgrades). If you can live with that, you'll be OK. If you can't afford > downtime, maybe compare the implied cost of downtime against the cost of > commercial options. > > On Mon, Nov 18, 2024 at 1:46 PM John Smith <java.dev....@gmail.com> wrote: > >> Actually the biggest feature we use is the "local" cache, where data is >> collocated/cached on the client. >> >> On Mon, Nov 18, 2024 at 2:33 PM John Smith <java.dev....@gmail.com> >> wrote: >> >>> Hummmm whats the best way to use Ignite as a central cache server then? >>> Cause We have quite a few thick clients so we can't just shut down >>> everything. Also, Blue/Green is prohibitively expensive (mostly >>> architecture and then "hardware resources") even with Ignite. >>> >>
