Hello Timothy I usually deploy on more servers, but just 2 to 4, I don't have larger deployments. I also have single server deployments. In my opinion and personal experience, native Java integration by Ignite with persistent storage is definitely better than a "hybrid" solution (some other software plus a Java client) like going to external caches like Redis. I've seen benchmarks in the past where Ignite also performed better. Don't know the current status as of today, but not my concern at all, as using Apache Ignite is definitely too easy and too fast to even consider alternatives. Some other developers may have had different experiences, just wanted to share my point of view.
Cheers Gianluca Il giorno mar 16 nov 2021 alle ore 04:33 Timothy Peng <timosp...@gmail.com> ha scritto: > @Surinder, @Ilya, > > Can you tell what's the advantages for memory storage compared to other > products such as Redis? > > Thanks. > > > On Tue, Nov 16, 2021 at 11:27 AM Surinder Mehra <redni...@gmail.com> > wrote: > >> So it is a very broad question. Sure you can use it for caching and >> compute as well as it has enough cores. Depending upon your requirements, >> you can read about data grid part on ignite documentation to get details >> about various ignite cache configurations >> - in memory >> - in memory with cache stores (IMDG) >> - caches with native persistence(IMDB) >> - on heap or off heap caches >> >> Just some pointers to read >> >> On Tue, Nov 16, 2021, 08:34 Timothy Peng <timosp...@gmail.com> wrote: >> >>> Hello >>> >>> I just have one dedicated server who has 128GB memory and 16 cores. >>> Can I deploy Ignite on this server and just use the memory cache feature? >>> >>> Thanks >>> >>
