Apache Ignite Pros and Cons

I love how easy to use the Apache Ignite API is, it's very intuitive and allows me to create a resilient distributed in-memory cache which is lightning fast. I really appreciate the quality of the documentation, taught me a lot! Review collected by and hosted on G2.com.

When I last used it, the ignite-zookeeper library was lagging behind the official zookeeper version significantly. I see that's changed a bit now, but still lagging a little (3.4.13 vs 3.5.6). However, the curator dependency is still severely outdated (2.9.1 vs 4.2.0). I needed to shade these in order to make progress on my distributed service. Review collected by and hosted on G2.com.

Creating a cache and getting started is not difficult. Rest communication to the cluster is good thing. In memory speed of computation is good Review collected by and hosted on G2.com.

Delicate rebalance mechanism. Issue of loading indice in memory on node restart. Wal related opacity in various parameters. Few cache configuration are mutable and few are not. Review collected by and hosted on G2.com.

Ignite is a large scale in-memory processing data processing system. It is similar to Spark but more flexible. Unlike RDDs Ignite collections are immutable. This means there is a lot you can do with Ignite such as using it as a cache or even for transaction processing. Review collected by and hosted on G2.com.

I found the documentation and starter material available for Ignite is not very comprehensive and helpful. Also, the server and distributed management of Ignite workers is not very streamlined yet. You need to manually ssh into servers to restart a worker or check logs when something goes wring Review collected by and hosted on G2.com.

We use Apache Ignite for our object cache, its a good cache for our ML models and helps us scale horizontally. Review collected by and hosted on G2.com.

Setup is a bit complicated and takes time, there is a learning curve Review collected by and hosted on G2.com.

Gives a lot of knobs to play with and suit it according to your needs. The underlying persistent layer can be switched. Review collected by and hosted on G2.com.

Setup wasn't straightforward like using a redis. I am yet to set it up properly via docker. Review collected by and hosted on G2.com.

Apache Ignite allows users to compute and store massive amounts of data at scale very reliably. While many classic SQL databases would choke on the high throughput demanded, Apache Ignite can easily handle huge throughput loads. Review collected by and hosted on G2.com.

Unless the data model is designed properly, a number of edge cases can cause unexpected poor performance when using Apache Ignite. Special care must be taken to determine what query patterns will be used. Review collected by and hosted on G2.com.

Robustness and durability of the application. Its extremely ease to use. Review collected by and hosted on G2.com.

Could have become more user friendly. In initial day of use, I found a little lost in the application Review collected by and hosted on G2.com.