Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsFor Spring Boot auto-configuration, follow Apache Ignite 2’s documented extensions: one for server or thick-client nodes and another for thin clients. Ignite 3 uses a different documented Java-client setup; the Ignite 2 Spring Boot extensions and configuration API should not be assumed to work with Ignite 3. This guide distinguishes the two paths so you can choose the one that matches your cluster and application.
Choose the Ignite version and connection mode first
Apache Ignite’s documented Spring Boot auto-configuration route is for Ignite 2. Its extensions can configure an Ignite server or thick-client node, or connect a thin client. Ignite 3’s documented Java quick start instead uses the Ignite 3 Java client. It does not establish compatibility with the Ignite 2 Spring Boot extensions.
| Path | What the application does | Configuration approach | Documented example details |
|---|---|---|---|
| Ignite 2 server or thick client | Creates an Ignite instance at Spring Boot startup. | Spring Boot properties, an IgniteConfiguration bean, or an IgniteConfigurer. |
Extension artifact version 1.0.0; properties use the ignite prefix. Apache Ignite Spring Boot documentation. |
| Ignite 2 thin client | Creates an IgniteClient connection at startup to a running cluster. |
Spring Boot properties, a ClientConfiguration bean, or an IgniteClientConfigurer. |
Extension artifact version 1.0.0; properties use ignite-client, with addresses required in the documented example. Apache Ignite Spring Boot documentation. |
| Ignite 3 Java client | Connects a Java application to an Ignite 3 cluster. | Ignite 3 Java client API; the cited quick start does not document Spring Boot auto-configuration. | Quick start uses org.apache.ignite:ignite-client:3.1.0, JDK 17 or later, Maven, and a three-node Docker Compose example. Apache Ignite 3 Java quick start. |
For an existing Ignite 2 application, use the matching Ignite 2 extension. For an Ignite 3 application, use Ignite 3 documentation and APIs rather than carrying over Ignite 2 extension coordinates or configuration classes.
Configure Spring Boot with Ignite 2
Apache documents two Maven extensions, both at version 1.0.0. Choose based on whether the application starts a node or connects as a thin client. The coordinates below are the extension versions shown in the Spring Boot integration documentation, not Ignite platform versions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Server or thick-client node
Add the autoconfiguration extension:
<dependency>
<groupId>org.apache.ignite</groupId>
<artifactId>ignite-spring-boot-autoconfigure-ext</artifactId>
<version>1.0.0</version>
</dependency>With the extension on the classpath, Spring Boot creates an Ignite instance at startup. The properties use the ignite prefix. For example, the documented property layout is:
ignite:
# Ignite properties go hereThe choice of Java configuration affects whether those properties are applied:
- Properties only: Configure through Spring Boot properties using the
igniteprefix. - Complete configuration bean: Provide an
IgniteConfigurationbean when you want to define the configuration in Java. In the documented example, properties do not configure this supplied object. - Configurer: Implement
IgniteConfigurerto modify the configuration loaded from the Spring Boot configuration file. This lets the application adjust property-based configuration programmatically.
These are alternatives, not three layers that automatically merge. Decide whether properties or a complete bean owns the configuration, and use the configurer when the intended starting point is the configuration loaded from properties.
Thin client
For a thin client, add the separate extension:
<dependency>
<groupId>org.apache.ignite</groupId>
<artifactId>ignite-spring-boot-thin-client-autoconfigure-ext</artifactId>
<version>1.0.0</version>
</dependency>This extension creates an IgniteClient connection on startup. Its property prefix is ignite-client; the documented example marks addresses as mandatory and shows this endpoint:
ignite-client:
addresses: 127.0.0.1:10800Use an address reachable from the Spring Boot process and replace the sample endpoint with the address of your running Ignite 2 cluster. The thin-client route also supports programmatic setup through a ClientConfiguration bean or an IgniteClientConfigurer.
Use Ignite 3 as a separate Java-client path
If your target is Ignite 3, the official Java quick start is the relevant starting point—not the Ignite 2 Spring Boot extension examples. It demonstrates a Maven application using org.apache.ignite:ignite-client:3.1.0 and connecting to a Docker Compose cluster.
Rank #4
Quick-start prerequisites and example footprint
- JDK 17 or later
- Maven
- Docker and Docker Compose
- A three-node cluster in the quick-start Compose example
Follow the Ignite 3 Java quick start for its project and connection steps. The documented quick start establishes a Java-client workflow; it does not document use of Ignite 2’s ignite or ignite-client Spring Boot property prefixes.
Check release status and keep version numbers in context
The Apache Ignite downloads page identifies Ignite 3.1.0 as the latest Ignite 3 release, dated 2025-10-21, and describes Ignite 2 as LTS, recommending it for existing deployments. Release status can change, so check the Apache Ignite downloads page when selecting versions.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Version numbers in examples refer to different things. The Spring Boot extensions are shown at version 1.0.0; the Ignite 3 quick start uses client dependency version 3.1.0. Separately, the Ignite 2 Maven setup page uses Ignite 2.18.0 as its example. That example is not evidence that 2.18.0 is the latest Ignite 2 release.
Keep adjacent Spring integrations separate
Spring Boot auto-configuration is not the same as Spring Data repositories or Spring transaction support. Ignite’s Spring Data integration is a separate Ignite 2 integration for repositories implementing Spring Data’s CrudRepository, with its own extension, core, indexing, and Spring dependencies. Spring transaction support is another separate extension. Add these only when the application needs repository or transaction integration; they are not prerequisites for the Boot setup described above.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
