Apache Ignite

Treat Ignite as a cluster-backed data layer, not as a file you embed in a unit test. The Java quick start documents Ignite 2.18.0, a Java 11 or 17 environment, and a binary distribution. From the bin directory, its example starts a local node with the sample configuration:

./ignite.sh ../examples/config/example-ignite.xml

A second terminal can start another node with the same configuration. For an application-level first task, add the documented Maven dependency and create a cache with a few key-value records:

// after connecting to Ignite
IgniteCache<Integer, String> cache = ignite.getOrCreateCache("demo");
cache.put(1, "ready");
String status = cache.get(1);

This is illustrative code, not a run result; the returned value for key 1 is the string ready. The example makes the data-access path concrete, but a useful evaluation should also test cluster configuration and persistence settings for the intended workload. The startup script supplies JVM module flags needed by the documented Java versions; a directly launched application may need those flags set explicitly.

The project documentation has separate Ignite 2 and Ignite 3 codebases. This entry follows the Ignite 2 quick start and does not combine the two APIs. Expect to plan node discovery, memory sizing, storage, and network security yourself.