What's New in GigaSpaces Version 17.0.0

Release Date: June-2024

This page describes product changes, along with new features and functionality for GigaSpaces release 17.0.0.


Upgrade to Java 17 and Spring 6

Java Upgrade

GigaSpaces has been upgraded to Java 17 as the upgrade Spring 6 (see below) requires Java 17 or higher. In addition, this upgrade leverages updated features and improvements in Java, providing enhanced performance, security, and functionality. Java 17 includes more advanced garbage collectionClosed Garbage collection (GC) is a form of automatic memory management. The garbage collector attempts to reclain memory that was allocated by the program, but is not longer referenced; such memory is called garbage. (GC) mechanisms. Advanced garbage collectors open more possibilities for managing our memory footprint. For additional information about GigaSpaces Java usage, refer to JVM Settings and Tuning.

Why not Java 21?

Java 21 was released in September 2023 and has not yet been widely adopted in the community. If GigaSpaces enforce Java 21 on the server side (XAP), there might be a bigger impact on our install base that we can anticipate. Our recommendation to existing customers would be to consider upgrading their client applications directly to Java 21 to support forward compatibility.

Spring Framework Upgrade

We have transitioned from Spring 5.3 to Spring 6. Upgrading to Spring 6 ensures continued compliance with security best practices and access to the latest patches and fixes.


Security Enhancements: The shift to Spring 6 addresses known security issues inherent in previous versions, aligning with our commitment to maintaining a secure and robust system.

End-of-Support Considerations: This move is driven by the upcoming end-of-support for Spring 5.3 in August 2024, ensuring we continue to receive necessary security updates and benefit from the latest features in the Spring ecosystem. .



  • Client Applications: This impacts all client applications which use Java SDK. Any applications which use .NET will be required to upgrade to Java 17.

  • Codebase and dependencies need to be updated to ensure compatibility with Java 17 and Spring 6.

  • Review and adjust custom implementations and third-party integrations to align with the updated frameworks.


  • Enhanced security and performance metrics due to the new Java and Spring versions.

  • Monitoring and adjustments may be required during the transition period to ensure system stability.

We encourage all users to thoroughly test their applications in the updated environment to identify and resolve any issues prior to deploying the changes in production.

For additional details, including upgrading from previous version, please contact our Customer Support team.


Q: Will backward compatibility be broken when moving to GigaSpaces version 17.0?

A: Existing XAP customers who upgrade to GigaSpaces version 17.0 will also need to upgrade their client applications to be compiled with Java 17 or higher

Q: If you are using an older GigaSpaces version, will GigaSpaces still support you?

A: Older versions will be supported as always, within policy or per an extended support contract. That said, any vulnerabilities resulting from 3rd party versions that are end-of-support (for example, Spring 5.3) will only be addressed by an upgrade to a supported version of the 3rd party. As result, this might force an upgrade to GigaSpaces version 17.0 unless the customer accepts the risks that will exist due to those vulnerabilities.


Service Account Privilege Management

GigaSpaces already secures user accounts by, for example, using IDP. This is now being expanded to include the securing of service accounts.

  • A Service Account  is an account that is typically used by an application or a compute workload. It is an application that wishes to access GigaSpaces resources. This could either be a user of applications or components that wish to access GigaSpaces APIs.

  • A service account differs to a user account in that it is associated with software that runs in our XAP Skyline or Smart DIH environments.

For additional information, refer to our Service Account Privilege Management page.

Data Integration (DI) Updates

This applies for Smart DIH.

Multiversion concurrency control (MVCC) is method that allows a user to have a concurrent and persistent view of distributed transactions across partitions. keep multiple versions of modified entries to ensure that a user has a persistent view of the data that is consistent with the SoR.

For additional information refer to our MVCC page.


GigaSpaces are introducing Transformations as part of our Data IntegrationClosed The Data Integration (DI) layer is a vital part of the Digital Integration Hub (DIH) platform. It is responsible for a wide range of data integration tasks such as ingesting data in batches or streaming data changes. This is performed in real-time from various sources and systems of record (SOR. The data then resides in the In-Memory Data Grid (IMDG), or Space, of the GigaSpaces Smart DIH platform. module. Configuring Transformations enables data to be converted into a simple format that can then be used for the easy creation of services.

  • A data pipeline is a method of transporting data from one place to another. Acting as a conduit for data, these pipelines will enable efficient processing, transformation, and delivery of data to the desired location.

  • Through data cleansing and Transformation processes, data pipelines enhance data quality and ensure accuracy for analysis and decision-making.

For additional information, refer to our Transformations page.

Batch Load (Feeders)

GigaSpaces now has the ability for Smart DIH to define batch loads via a standard pipeline interface.

For additional information, refer to our Batch Load page.