Infinispan 16.1
"Polly Want a Pilsner"
Infinispan 16.1 is here, and it is codenamed "Polly Want a Pilsner".
It is the first release that follows our time-boxed plan.
Container-based eviction
Prior to this release, it was only possible to configure memory bounds for individual caches.
Infinispan 16.1 introduces the concept of bounded memory containers: configure a global container (you can have more than one), and whether you want it to be bound by count or by memory and reference that container name in the cache configuration.
The following diagram shows the difference between per-cache and container eviction
In the example below, the memory configuration for caches a and b combined will be bounded at 100MB:
<infinispan>
<cache-container>
<eviction-containers>
<max-size-container name="max-size" size="100MB"/>
</eviction-containers>
<local-cache name="a">
<memory eviction-container="max-size"/>
</local-cache>
<local-cache name="b">
<memory eviction-container="max-size"/>
</local-cache>
</cache-container>
</infinispan>OpenAPI / Swagger
Infinispan 10 introduced the v2 REST endpoint which aimed to improve the original API and expand it with all the
requirements we added for data and system management. Unfortunately that API was designed in a way that made it
impossible to represent via an OpenAPI descriptor.
Infinispan 16.1 introduces a new v3 REST API which is OpenAPI-compliant.
To try it out, start an Infinispan Server and point to http://127.0.0.1:11222/swagger-ui/
Query and Lucene 10
Thanks to the work done by our friends over at Hibernate Search, Infinispan now supports both Lucene 9 and 10.
Infinispan Server
Server now requires Java 25
Our server image has already included Java 25 since 16.0, but we’ve now made this a hard requirement for bare metal deployments too. Don’t worry: the clients can continue running with ye olde legacy Java versions of choice.
Lucene 10.3
By requiring Java 25, the server can now include Lucene 10.3, which can leverage SIMD to increase performance in several areas.
Pre-start batch scripts
The server can now automatically execute batch scripts before start. This feature is primarily intended for our operator in order to prepare the server according to its configuration, but it may also be useful for your own use-cases.
AOT cache in the container image
The server image now includes an AOT cache to reduce startup and warmup time.
CLI batch error handling
The CLI has been enhanced to better report errors during batch execution: you can now decide to fail-fast, fail-at-end or ignore batch errors altogether.
Default mechanisms
Infinispan Server no longer enables weak/vulnerable authentication mechanisms by default: algorithms which use
MD5 and SHA-1 must be explicitly enabled if you want to keep using them.
Backwards compatibility
Infinispan 16.1 is fully backwards compatible with 16.0 deployments.
The next release
According to our roadmap, our next release will be 16.2, and it will happen on 2026-06-03.
Release notes
You can look at the release notes to see what was changed since our previous release.
Get them from our download page.
Get it, Use it, Ask us!
We’re hard at work on new features, improvements and fixes, so watch this space for more announcements!Please, download and test the latest release.
The source code is hosted on GitHub. If you need to report a bug or request a new feature, look for a similar one on our GitHub issues tracker. If you don’t find any, create a new issue.
If you have questions, are experiencing a bug or want advice on using Infinispan, you can use GitHub discussions. We will do our best to answer you as soon as we can.
The Infinispan community uses Zulip for real-time communications. Join us using either a web-browser or a dedicated application on the Infinispan chat.
Tristan Tarrant
Tristan is the Infinispan lead. He's been a passionate open-source advocate and contributor for over three decades.
